Component-based architecture vs Model View Controller (MVC)?

MVC frameworks like Laravel and Symphony have developed to have back-end technology and front-end capabilities through templating and similar features. They didn’t just build back-end capabilities because they understood the need to be able to provide user experiences.

However, component-based architectures arose because with MVC architecture, some things were hard to reuse. Component-based architectures made it easier to separate concerns and provide this usability.

Component-based architecture has provided frameworks like jQuery, which allowed you to create more interactivity on a browser and create interactions that weren’t otherwise possible. And that’s now expanded into Vue, Angular, and others that approach the problem from a design perspective rather than a back-end perspective.

While back-end and front-end frameworks seem like competing forces, the future of a CMS is always going to need a bit of both.

Back-end frameworks are necessary to create business logic, processing information, and storing information. Front-end frameworks are required to create the ability to capture data from the back-end or any other system and deliver it to the user as seamlessly and intuitively as possible.