Let’s talk software architecture. Most of us know MVC, it’s the foundation for pretty much every web framework. As your product grows though, problems with MVC will start to appear. Even a relatively simple product can end up with a bloated and messy codebase. MVC is where we start, but what do you do when you need to evolve past it?
Before we go further, let’s examine why we have so much trouble explaining the answer.
Here’s a common conversation (for developers anyway):
Read more at dev.to
