In a production environment where we expect to receive thousands or millions of concurrent connections to the backend service, this can quickly exceed your memory resources (or if you have a scalable cloud, it can get very expensive very quickly).īecause each time a client attempts to access a backend service, it requires OS resources to create, maintain, and close connections to the datastore. With PostgreSQL, each new connection can take up to 1.3MB in memory. Most web services are backed by relational database servers such as Postgres or MySQL. But you can further improve performance by pooling users’ connections to a database.Ĭlient users need to create a connection to a web service before they can perform CRUD operations. Caching frequently-accessed queries in memory or via a database can optimize write/read performance and reduce network latency, especially for heavy-workload applications, such as gaming services and Q&A portals. We tend to rely on caching solutions to improve database performance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |