R
R
ruboss2016-10-07 09:10:02
PHP
ruboss, 2016-10-07 09:10:02

How to properly build the application structure on the backend (good practice)?

Hello!
There is a web application, at the moment it has 3 databases, access to which is needed from several parts of this application. Interested in good practice, how to properly structure the project so that there is no code repetition and scalability and flexibility remain)
Outline of the current state of affairs in the project
9f354252dc0e43ba9776acb224bbacf5.PNG
There is a certain admin panel through which data is received and written to the database, either directly through it or through the main part of the application.
There is an idea to do everything through the API and just make requests to it.
4cf7ed8ddae249ae9eca2c1ba0fec4e8.PNG
What could be the disadvantages of this approach?
Tell me where to dig or what to read?)

Answer the question

In order to leave comments, you need to log in

1 answer(s)
R
romy4, 2016-10-07
@romy4

I am for the second option - it is more flexible and you separate the front from the back completely.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question