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:
Software Architecture Monday: https://bit.ly/3dadEe3
Fundamentals of Software Architecture: https://amzn.to/3rgFLjY
Software Architecture: The Hard Parts: https://amzn.to/3BjMMF2