I have been reading a lot of post about PHP and wich framework is the best nowadays. Many developers said that Laravel is the winner. Other prefer Symfony or Drupal. There are a lot of reason to decide using one despite another. But I have not read nothing about the separation of backend and frontend.
When I started my career we used to mix the back and the front in the same project. In my case (using Symfony) I developed a lot of webapps using the TWIG template system. Mixing backend and frontend code in the same file. That was the way we get used to be. It worked and there was no reason to change.
After a couple of years I decided to separate a little bit the responsability and I started using frontend frameworks (Angular, jQuery) to call the backend service and returning just json data from the back. In the end the frontend was server by the backend that was serving data to the frontend (booom). It was a step to be closer to my new setup.
After a few projects injecting Vue in the frontend side, we decide to separate completely the front from the back. This was a natural step because the projects we developed were usually based on a native mobile/web experience and the same API develop for the smartphone apps could be consumed by the web side. This decision was a point in our organization.
Now we are able to undestand the scope of a project and we can separate and distribute the develop flow more efficiently than the time we mixed front and back at the same time
Top comments (0)