Use Pool instead of Client from postgres module #77
Labels
⚙️ backend
Related to the backend (NodeJS, Docker, Build)
⚡ new
New tasks that were recently added and need attention from project management
Milestone
Description
The backend uses a single
Client
for all queries to the database in a single shop. It could use thePool
and work with just a couple of connections for all shops of an instance.Links/References
(Add any designs, screenshots or links that helpful to implement the feature)
Tasks
prefix
"connection"Additional Context
The current architecture should work for a couple of shops if there are not too many people reserving slots at the same time. Using a
Pool
instead would make it scale better if you decide to host multiple highly frequented shops.The text was updated successfully, but these errors were encountered: