Tag: messaging

In this blog, I present the scatter-gather pattern, which is a composite pattern based on pub-sub and point-to-point messaging channels. It also employs correlation ID and return address. I show how this is implemented in the Wild Rydes example application. You can use this integration pattern for communication in your microservices.

Queues, publish/subscribe services, and event buses are important parts of a resilient, well-architected serverless application. These are provided in AWS by SQS, SNS, and EventBridge.

Messaging is an important part of serverless applications and AWS services provide queues, publish/subscribe, and event routing capabilities. This post reviews the main features of SNS, SQS, and EventBridge and how they provide different capabilities for your workloads.

This post is contributed by Mithun Mallick, Solutions Architect and Christian Mueller, Solutions Architect Message-oriented middleware (MOM), or message brokers, are the backbone that integrates business critical applications in many industries. MOMs are used to integrate systems like inventory management, payment systems, and CRM systems. They are also used to orchestrate order-processing workflows across multiple systems, […]

This post is courtesy of Dirk Fröhner, Sr. Solutions Architect The first blog in this series introduced asynchronous messaging for building loosely coupled systems that can scale, operate, and evolve individually. It considered messaging as a communications model for microservices architectures. This post covers concrete architectural considerations, focusing on the messaging architecture. Part 3 covers running […]

This post is courtesy of Dirk Fröhner, Sr. Solutions Architect One of the implications of applying the microservices architectural style is that much communication between components happens over the network. After all, your microservices landscape is a distributed system. To achieve the promises of microservices, such as being able to individually scale, operate, and evolve each service, this […]

This post is courtesy of Otavio Ferreira, Sr Manager, SNS. In a postal system, a dead-letter office is a facility for processing undeliverable mail. In pub/sub messaging, a dead-letter queue (DLQ) is a queue to which messages published to a topic can be sent, in case those messages cannot be delivered to a subscribed endpoint. […]

Update – Nov 9, 2021: AmazonMQ also supports RabbitMQ – read Creating static custom domain endpoints with Amazon MQ for RabbitMQ for more information This post is courtesy of Wallace Printz, Senior Solutions Architect, AWS, and Christian Mueller, Senior Solutions Architect, AWS. Many cloud-native application architectures take advantage of the point-to-point and publish-subscribe (“pub-sub”) model of message-based […]

This post is contributed by Robin Salkeld, Sr. Software Development Engineer Amazon SQS is a fully managed message queuing service that makes it easy to decouple and scale microservices, distributed systems, and serverless applications. Asynchronous workflows have always been the primary use case for SQS. Using queues ensures one component can keep running smoothly without losing […]

This post is courtesy of Christian Mueller, Sr. Solutions Architect, AWS and Dirk Fröhner, Sr. Solutions Architect, AWS At AWS, we see our customers increasingly moving toward managed services to reduce the time and money that they spend managing infrastructure. This also applies to the messaging domain, where AWS provides a collection of managed services. Asynchronous messaging is […]