Application Integration Patterns for Microservices - Level 300 (United States)

When you have a microservices architectural style, much of the communication between components is done over the network. In order to achieve what microservices promise, this communication must happen in a loosely coupled manner. In this session, we discuss some fundamental application integration patterns mostly based on messaging, and we connect them to real-world use cases in a microservices scenario. We also highlight the benefits that asynchronous messaging can have over REST APIs for communication between microservices.
Learn more about AWS at - amzn.to/2ZueGNO
Subscribe:
More AWS videos bit.ly/2O3zS75
More AWS events videos bit.ly/316g9t4
#AWS #AWSSummit #AWSEvents

[@architectelevator]

It would be a nice touch to reference Enterprise Integration Patterns. Much of that material (icons, names) is available under CC BY, so it's fine to be used in corporate presentations.

[@ansariBE]

can you point me to the materials? I've been looking for the architectural patterns and tech stacks for integrating multiple enterprise applications.

[@Superedit2214q]

Superb session.

[@amazonwebservices]

Thank you! 💚

[@animatem]

I thought it was a good overview. In essence, I expect all my integration architects to be familiar with all these patterns. Every so often, I like to review them myself to make sure nothing new has been added that I need to know about.

[@Asgardinho]

wouldn't be better to use kinesis instead on SNS+multiple SQS ?

[@Superedit2214q]

Kinesis is used as a replacement for ETL tool to pull large amount of data and ingest them into object store S3. The write is fast as it is object storage.