Splitting up a Monolith to (micro)Services

Splitting up a Monolith into (micro)services is not an easy task. It can be broken apart into multiple steps. Defining boundaries and capabilities are key. Depending how much coupling you have within your Monolith, and how you couple is a big factor.

🔔 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/splitting-up-a-monolith-into-microservices/
👋 Twitter: https://twitter.com/codeopinion
✨ LinkedIn: https://www.linkedin.com/in/dcomartin/

0:00 Intro
0:22 Coupling
2:28 Boundaries
3:43 Communication
5:00 Database Separation
5:46 Async Messaging
7:01 Saga / Message Driven

📝 Context is King: Finding Service Boundaries
https://codeopinion.com/context-is-king-finding-service-boundaries/

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#softwarearchitecture #microservices #eventdrivenarchitecture