We are trying to find the best solution for working with a slow database on a website.
The basic system architecture is as follows:
- Slow (some readings and most records are fast, others take a few seconds). Postgres DB. We have no control over this.
- A monolithic autonomous system that accesses Postgres DB. We have no control over this.
- Fast internal server (s) that can access the Postgres database. We can develop and install software for this server.
- Fast web server (s) running a LAMP stack that can NOT access the Postgres database, but can access the internal server. We can develop software for this server.
- Fast MySQL database that can be accessed. We have full control over this.
We are developing a new web application for working on web servers using Symfony 2.
Our initial plan was to create a RESTful API to run on the internal server that is consumed by the web application. The main problem we are facing is that the speed of the web application is limited by the speed of DB Postgres, which is unacceptable to users.
Does anyone know any strategies to solve this speed problem?
- , , , , , . , , . , API , Postgres. , , Postgres. - , , .
JSON-LD , , , , , . , .
:
!