AWS re:Invent 2022 - Application integration patterns for microservices (API303-R)

Virtually all integration approaches come with trade-offs. However, loosely coupled integration can help you design independent systems that can be developed and operated individually and can also increase the availability and reliability of the overall system landscape-particularly by using asynchronous communication. While there are many approaches for integration and conversation scenarios, it’s not always clear which approach is best for a given situation. Join this session to learn about foundational patterns for integration and conversation scenarios with an emphasis on loose coupling and asynchronous communication. Explore real-world use cases architected with cloud-native and serverless services, and get guidance on choosing integration technology.
Learn more about AWS re:Invent at go.aws/3ikK4dD.
Subscribe:
More AWS videos bit.ly/2O3zS75
More AWS events videos bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
#reInvent2022 #AWSreInvent2022 #AWSEvents

[@nettech5]

Every year I watch this amazing session, do reinforce my learning and get the latest updated.

[@Praveenkumar-vg3pn]

For someone like me who has very little to no knowledge on Architecture/patterns .. This talk very informative and curious provoking !!!

[@vladimirtrushkin6302]

Just 2 cents about integration via database. It may also prove to be an expensive pattern.

[@dirkfrohner8771]

It is a terrible pattern from whatever angle you look at it. 🙂

[@brijeshmondal_]

In 3rd use case actually share DB in multiple service which may not be ideal.

[@dirkfrohner8771]

No DB is actually being shared, but apparently the diagram doesn't point this out well enough - thanks for the feedback.