Answer the question
In order to leave comments, you need to log in
Is it better to connect the WEB interface to the API or directly to the database?
Let's assume, some highly loaded service is developed. Development is carried out on "PHP" using the "MySQL" DBMS (we will immediately cover the topic of the disadvantages of these solutions). The service will have an API for mobile applications and developments of third-party clients, as well as a browser-based WEB interface (in other words, a site that provides the same functionality as applications).
Question: what data source is more acceptable for the WEB-interface of the service - the API of the same service or directly the database? Personally, I'm leaning towards the version with the connection of the WEB-interface to the API, since the need for duplicating the recording / output of information, error handling conditions, etc. is removed; but you will probably have your own opinion on this matter ...
Answer the question
In order to leave comments, you need to log in
1. A single RestAPI - we divide it into private (for ourselves and the backend) and public (for any custom clients).
2. We write a website and connect it as one of the clients.
3. RestAPI - controls accesses and communicates with the database.
Add-on for RestAPI: here
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question