Amazon Web Services offers the Amazon Simple Notification Service (SNS) which provides pub/sub messaging and push notifications to iOS and Android devices. It is meant to operate in a microservices architecture and which can support event-driven contingencies and support the decoupling of applications.
$0.01
per 1 million
Appian
Score 8.2 out of 10
N/A
Appian is a low-code development and business process management platform. It features drag-and-drop design for app building, automated work processes, unified data management, and cloud-based deployment.
$0
Aurea Process
Score 10.0 out of 10
N/A
Aurea Process (formerly CX Process) from Aurea Software in Austin is a business process management offering, based on Savvion BPM.
$200,000
per year
Pricing
Amazon Simple Notification Service (SNS)
Appian
Aurea Process
Editions & Modules
API Requests & Payload Data
$0.01
per 1 million
API Requests
$0.50
per 1 million requests
Notification Deliveries
$0.50
per million notifications
Appian Community Edition
$0
Application - Input-Only
$2
per month per user
Application - Infrequent
$9
per month per user
Application - Standard
$75
per month per user
Platform
Custom Quote Priced per user with unlimited apps.
minimum 100 users, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
unlimited
Platform
Custom Quote Priced per user with unlimited apps.
Minimum 100, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
Unlimited
License
$200,000
per year
Offerings
Pricing Offerings
Amazon SNS
Appian
Aurea Process
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Amazon Simple Notification Service (SNS)
Appian
Aurea Process
Features
Amazon Simple Notification Service (SNS)
Appian
Aurea Process
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
Amazon Simple Notification Service (SNS)
-
Ratings
Appian
9.1
75 Ratings
8% above category average
Aurea Process
-
Ratings
Visual Modeling
00 Ratings
8.873 Ratings
00 Ratings
Drag-and-drop Interfaces
00 Ratings
8.972 Ratings
00 Ratings
Platform Security
00 Ratings
9.271 Ratings
00 Ratings
Platform User Management
00 Ratings
8.872 Ratings
00 Ratings
Reusability
00 Ratings
9.575 Ratings
00 Ratings
Platform Scalability
00 Ratings
9.573 Ratings
00 Ratings
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Amazon Simple Notification Service (SNS)
-
Ratings
Appian
-
Ratings
Aurea Process
5.3
1 Ratings
37% below category average
Dashboards
00 Ratings
00 Ratings
6.01 Ratings
Standard reports
00 Ratings
00 Ratings
6.01 Ratings
Custom reports
00 Ratings
00 Ratings
4.01 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Amazon Simple Notification Service (SNS)
-
Ratings
Appian
-
Ratings
Aurea Process
5.8
1 Ratings
36% below category average
Process designer
00 Ratings
00 Ratings
6.01 Ratings
Process simulation
00 Ratings
00 Ratings
7.01 Ratings
Business rules engine
00 Ratings
00 Ratings
5.01 Ratings
SOA support
00 Ratings
00 Ratings
5.01 Ratings
Process player
00 Ratings
00 Ratings
7.01 Ratings
Model execution
00 Ratings
00 Ratings
5.01 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Amazon Simple Notification Service (SNS)
-
Ratings
Appian
-
Ratings
Aurea Process
4.0
1 Ratings
70% below category average
Social collaboration tools
00 Ratings
00 Ratings
4.01 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
The Amazon SNS service is well suited to support event notifications, monitoring applications, workflow systems, time-sensitive information updates, and mobile applications that generates or consumes notifications. It can be used to relay time-critical events to mobile applications and devices. It provides significant advantages to developers who build mobile applications that rely on real-time events. It is not well suited for hybrid cross platform mobile application frameworks at this juncture. An optimal version to meet the needs of a cross platform mobile developer is needed as generally the frameworks are not meant to manage real-time events. It is also not suited for cases where the queue management needs improvement or requires special workflows/tooling.
Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.
The tool has potential. Its capabilities and visual aspects could be considered rather basic but this might improve, particularly if the business intelligence/analytics aspect is leveraged. Once running well, it could allow (perhaps smaller) companies to successfully improve their customers' experiences through digitalizing customer journey - and we all know that customer loyalty goes a long way. However, whether or not the tool is comprehensive enough to deliver this for larger companies with more complex, multi- and omni-channel interactions is yet to be seen...
Allows at a glance workflow documentation which assists in the need we have for information readiation.
Drag and drop interface for workflow development greatly speeds our apps time to market.
Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.
At times you receive access denied errors which are annoying.
Rarely do you receive internal failure errors where you can't access the information. It is rare but it does happen.
You are required to add an MWS Authentication Token every so often. I wish it would pull that information automatically for you so you don't have to go searching for it.
Search issues when type ahead and database search are used in the same field.
Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.
We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian
It is useful for applications developed using event driven architecture. It helps in tracking and logging the events in a very timely and efficient manner. The dashboards are a little difficult to implement. But overall it is very easy to integrate with other AWS services like Lambda, API GW, S3 and DynamoDB. The permissions to access should be resolved before using it.
Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.
Amazon Simple Notification Sevices (SNS) support depends on your usage pattern and definitely on your support plan as an enterprise with AWS. Before reaching out to support you should read their documentation, as they have mentioned almost all the common issues and their solutions there. However, for specific issues, they generally respond in 1-2 business days.
Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.
As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.
Amazon’s SNS is incredibly easy to set up compared to the more powerful, but complex, Kafka flavours.
SNS’s core advantages are –
· no setup/no maintenance
· either a queue (SQS) or a topic (SNS)
· various limitations (on size, how long a message lives, etc)
· limited throughput: you can do batch and concurrent requests, but still achieving high throughputs would be expensive
· SNS has notifications for email, SMS, SQS, HTTP built-in.
· no "message stream" concept Overall, it would be the best choice to get into the concepts of Pub/Sub concepts as although it has limitations it can provide significant capabilities and solutions
Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?
Amazon Simple Notification Service (SNS) saved us a lot of extra coding time by providing straightforward functionality we needed in our ad campaign automation tool.
Amazon Simple Notification Service (SNS) allows us to maintain a consistent, serverless model within our applications.
I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.
As our customers vary in size and maturity, the ROI ranges accordingly.
For younger, smaller businesses this is a useful tool. Digitalization of he customer journey has certainly helped save time and efforts in many cases.
For more mature market players the tool is not always comprehensive enough. Dashboard and report personalization take time and efforts, and sometimes it feels that a dedicated BI tool would be a more suitable solution.