Back to Basics: Transaction Patterns for Distributed Applications

When dealing with transaction patterns, the traditional monolithic application creates tightly coupled transactions dependent on the successful completion of a preceding action. This sequence can cause some very undesirable delays in applications. In this episode, join Derek as he breaks down the advantages of implementing a modern distributed application pattern to reduce the issues around coupling while also allowing the services themselves to be built and run on different platforms, services, and technologies. The utilization of AWS Step Functions as the orchestrator also gives a nice visual representation of the flow that will make transaction tracing and debugging easier.
Additional Resources:
Decompose by transactions - AWS Prescriptive Guidance: docs.aws.amazon.com/prescript...
Implement the serverless saga pattern by using AWS Step Functions - AWS Prescriptive Guidance: docs.aws.amazon.com/prescript...
Building a serverless distributed application using a saga orchestration pattern | Amazon Web Services: aws.amazon.com/blogs/compute/...
Saga pattern - AWS Prescriptive Guidance: docs.aws.amazon.com/prescript...
Check out more resources for architecting in the #AWS cloud:
amzn.to/3qXIsWN
#AWS #AmazonWebServices #CloudComputing #BackToBasics #DistributedApplications

[@raclemonte68]

Great stuff; always a pleasure to absorb mr Bingham’s presentations. Derek has a great flair for explaining non-trivial concepts clearly. Inspiring me towards putting step functions into action.

[@muswain]

Nice one Derek with so clear n articulate explanation. Really love Step Functions with its workflow/orchestration capabilities. One of the best AWS services for a wide variety of use cases

[@murunatan6661]

SAGA pattern is conceptually hard to understand even for experienced developers. Your explanation was lucid and easy to grasp. AWS step functions for transaction orchestration stuck in my head.

[@chiomaokafor3892]

Beautiful video..Thanks for sharing..

[@hankwk]

Good explaination. As an aside, SAGA also enables the ability for the customer or user to check on the status of their request through the orchestrator if built-in.

[@somakkamos]

Wowwww best explanation of not only saga but also how distributed transactions are such jerks 😝
Thank you for the crisp and clear video

[@andresdigi25]

Amazing. I was wondering which services in aws i can use to implement a saga pattern. Thanks

[@ciarancallaghan3810]

What software do you use for the animations in this video?