laravel - PHP: as API+Views or just API -


note: opinionated question. m asking unable find proper articles covering concern.

php (alone or framework laravel) can used both backend , frontend (with templating engines blade,smarty,etc) development.

my concern is:

  1. is use templating engine , create views in php?
  2. use php backend tech , create apis, let frontend built in other language (like angular,react,etc) chosen front end developer.
  3. if use templating-engine, application getting tightly coupled between frontend tech choices , backend tech choices?

ps: hope concern clear, if not explain in elaborated way.

my opinion: if building small-medium size web project, don't bother use frontend frameworks, because don't horses in such small environment. when comes larger project scaling - recommended use kind of frontend framework, because kind of project (or should be) maintained team, backenders can focus on backend - frontenders on frontend.

a lot of folks says web developer web developer, there no backend or frontend. in opinion, not faced kind of project need separate things.

you can @ or can master , specific niche, choose path wisely.


Comments

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -