5 Software Architecture Mistakes That Make Systems Hard to Change
- by Derek Comartin
- Published on Derek Comartin (CodeOpinion)
- Curated on
- Uncategorized
You can follow every enterprise best practice. You can use Clean Architecture, some type of layered architecture, event-driven architecture, microservices, or whatever else is popular.
It can still end up in the same place.
You have a system that is really hard to change.
YouTube
Check out my YouTube channel, where I post all kinds of content on Software Architecture & Design, including this video showing everything in this post.
When you do make a change, you are afraid you are going to break something. Eventually, the same comment keeps coming up:
We would be better off rewriting this whole thing.
The codebase might not even look that bad. It might be organized and relatively easy to follow. Except it is not easy to follow when you actually need to change it. That is when everything becomes convoluted and complicated.
One of the reasons is probably one of these five architectural decisions. In each case, you are making an expensive decision without having enough information.…