Group 4 Created with Sketch.
Episode 36 of 70

#36: Microservices architecture: principles and how to break them

04:11
Play Audio
Add to Playlist
Share Report
Snippets are a new way to share audio!
You can clip a small part of any file to share, add to playlist, and transcribe automatically. Just click the to create your snippet!
Top Snippets - #36: Microservices architecture: principles and how to break them
Found on these Playlists
Add to Playlist
Full Description
Back to Top
Microservices are contrasted to a monolith. Single, large application that implement the whole system. Typically hard to understand, develop, test and deploy. Monoliths tend to become a big ball of mud with each component referencing every other. The idea behind microservices is to split your complex system into multiple independent applications. Small and agile. They communicate with each other via APIs but are otherwise highly decoupled. The independence and decoupling has many aspects: deployment, languages and frameworks, storage, organization. Most importantly, each microservice should be self-sufficient to a reasonable degree. Let’s discuss what it means and how often these aspects are violated.
Read more: https://256.nurkiewicz.com/36
Get the new episode straight to your mailbox: https://256.nurkiewicz.com/newsletter