Lesson 161 - Agility and Monolithic Architectures

During the past three lessons I’ve talked about some of the more common monolithic architecture styles. One question that has come up is why these architecture styles should be used when you have tight budget and time constraints, but should not be used if you have high time-to-market needs (getting changes out as fast as possible to your end uses). Realizing I created a bit of confusion about this, I decided to interrupt our architecture style journey and address this question about simplicity vs. agility and explain why those guidelines are the way they are.

Reference Links:

[HAMYLABS]

It's interesting because the testability portion can kinda side either way. For monoliths it may actually be easier to get higher coverage because you can test everything together. Moreover you can actually use code tools to discover all usages whereas in a distributed microservice across several repos it may literally be impossible to find all code usages of your service.

[ren.oooooo]

Now i understand why most companies want their monoliths to move to microservices and others want their microservices to regress into monoliths