If you're working in a distributed application, you're bound to run into a design issue where you want data consistency between services. But you don't have a distributed transaction, so what's the solution? In this video, I will take an example use case and explain the design challenge and solutions for handling communication and consistency between services.
🔗 EventStoreDB
https://eventsto.re/codeopinion
🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1
💥 Join this channel to get access to source code & demos!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join
🔥 Don't have the JOIN button? Support me on Patreon!
https://www.patreon.com/codeopinion
📝 Blog: https://codeopinion.com
👋 Twitter: https://twitter.com/codeopinion
✨ LinkedIn: https://www.linkedin.com/in/dcomartin/
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion
0:00 Intro
0:47 Context Use-Case
2:33 Synchronous Callback
4:52 Async Request-Reply
7:23 Reservation
8:54 Boundaries
Async Request Reply
https://www.youtube.com/watch?v=6UC6btG3wVI
Process icons created by Freepik - Flaticon
https://www.flaticon.com/free-icons/process
#softwaredesign #softwarearchitecture #distributedsystems
