Why not build the front end using WordPress with Angular. And build the backend with Laravel and VueJS. Or, the other way around? What do this even mean?
What do people mean by Back-end and Front-end in software development? It can be M vs VC or it can mean a database vs a display terminal, or it can mean the communications relationship responsibility and rules you apply to open channels between modules. Lost you yet?
Software can be hard to maintain if it is constructed in a monolithic fashion.
Or, software can comprise individually constructed components that interact, supported by backend state recording and other processes. Messages are the bits of memory flying between the clusters of logic. The reason the “dashboard” metaphor gets so much use if that it reflects this model. We want to see and control the software from one place.
The software we use to create environments that are constructed in this way are more resilient to change as they are always being made to work properly with a current set of scheduled changes.
“Reusable software” is a bit of a scam. It is not that you can literally reuse the universe of software assuming everything perfected needs to be forgotten about and simply linked to in various documented service connections. It is in the design of a software module: a concept of code reusability is important, but you do not have to do it just for the sake of it. Sometimes it is better to write with other priorities: speed, results, accuracy, and testability may be important, but generally will become less of a problem if you develop with usability as the primary objective.
We segment software into MVC patterns and the like because we know they fit the functionality we are looking for, abstractions are useful as we can fit them together.
