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
TIBCO Messaging
Score 8.1 out of 10
N/A
TIBCO offers high-performance messaging technology, and gives customers flexibility and unique choice between Commercial and Open-source messaging solutions. TIBCO Messaging is a comprehensive messaging portfolio available to meet a wide variety of use cases and deployment models.
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.
If you need a robust, extensible, reliable Enterprise Service Bus, with "Enterprise" being the key word here, TIBCO [Enterprise Message Service] will be able to fulfill every expectation. As proof of concept, or ad-hoc implementations, it might not be as well suited due to the infrastructure required.
Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone.
Tibco EMS scales well, and this is another of our stringent requirements.
Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape.
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.
In terms of TIBCO Messaging, it would nice to have a more out-of-the-box way of linking its objects (queues, topics) directly to those of other popular solutions like MQ or Kafka.
Not being able to filter (that is, using selectors) through patterns/subtexts on the message body is missed on occasions.
Given the current trends and state-of-art, lift & shift of on-premise EMS clusters to cloud architectures should be more directly attainable.
EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance.
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.
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.
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
We also use other messaging products: IBM MQ, especially for integration with other systems (server2server), which has been an industry standard for a long time, and Apache Kafka for cloud-native applications. EMS is a worse option compared to them, but it is still acceptable.
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.
