The Airship Experience Platform provides an end-to-end solution for unifying experiences across channels and capturing value across the entire customer lifecycle.
N/A
Amazon SNS
Score 8.8 out of 10
N/A
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
Oracle SOA Suite
Score 8.0 out of 10
N/A
The rapid adoption of cloud-based applications by the enterprise, combined with organizations’ desire to integrate applications with mobile technologies, is dramatically increasing application integration complexity. Oracle SOA Suite 12c, the latest version of the company's unified application integration and SOA solution, offers a simplified cloud, mobile, on-premises and Internet of Things (IoT) integration capabilities within a single platform.
Well-Suited for: 1. Mobile App Notifications: Ideal for targeted push notifications in apps. 2. Customer Segmentation: Effective for personalized marketing campaigns based on user data. 3. Event-Triggered Automation: Great for automated messaging based on user actions. 4. A/B Testing: Useful for optimizing campaign messages and strategies. Less Appropriate for: 1. Non-Mobile Channels: Less effective if the primary focus is on non-mobile communications like email or direct mail. 2. Basic Email Marketing: Other platforms might be better suited for simple, broad email campaigns without complex segmentation or personalization needs.
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.
Oracle service bus is great to quickly proxy any legacy services exposed as soap service. It's well suited for aggregating multiple services on a single endpoint. We can point to multiple endpoints on the business service and use a round-robin approach to access the endpoints. It's not well suited for data transformation and quick preview of mappings and transformations. It's not great on path to cloud transformation.
The marketing push notifications are very effective, and it gives us free hand to define different business criteria to target user groups
The user experience or the message content could differ from Android and iOS, and this is a huge benefit for us
As an Architect, troubleshooting an issue is very detailed and the time it takes to troubleshoot an issue is considerably less from our previous product
The Oracle Service Bus makes the management of web services extremely easy. Through its point and click interface, the web service endpoints can be easily modified.
The administration console provides useful dashboards to diagnose any service issues.
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.
Message reporting tied to a database seems counter productive. Better options to eliminate that would not only minimize the maintenance hassle but also gives more ease to manage the product.
Polling feature isn't very efficient where the end point JMS queues may still have JMS connections despite not enabling the corresponding poller proxy services.
Unable to deploy multiple web services in one go from the OSB Web console.
We have had not many issues with Oracle Service Bus and it's very stable for our requirements. It's highly available and helps us implement Tier1 applications on it.
The interface takes a bit getting used to in order to know how to take advantage of everything. Some of the analytics that are available are particularly hard to find, so it's important to pay attention when customer support reviews everything, but everything I'd want and need in terms of Push and In-App messaging is all there.
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.
It's an excellent enterprise service bus and has very stable features. We have been using it since 2008. We did hit into some issues. But, recreating the service helped fix many issues. Also, deployment to various environments was easy. Also, the plugin on Eclipse helps to build proxy and business services quick and easy.
I have not had to interact much with customer support as I have been able to find the vast majority of the answers I'm looking for within their documentation, which I very much appreciate because it saves me a lot of time. Customer support has been responsive and helpful for the most part during the couple of interactions I've had.
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.
We had some issues with MQ connectivity through OSB and our experience was poor with the support team. They do respond. But, it felt like we are ignored and we had bad support. We had to escalate and things used to get dragged for weeks before we get more quality questions on how to pursue investigation.
We've tested a bunch of different CRM tools over the years and Airship has been a winner for its functionality, features, cost, and ability to integrate with other softwares that we use. It has been great for SMS and mobile in particular. It could certainly be a one stop shop for CRM.
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
The ROI has increased more than approx. 50% (exact details to be confirmed) based on cross-channel orchestration
Using push notifications alone, we have seen a huge increase in app engagement which was a challenge before to nudge users to get back to the App after initial download
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.
