Anton Komarov
Reputation: 163
What the consequences might be from opening and closing connections to DB on every http request
I have a huge project where data access layer opens and closes connections on every http request or even more frequently. A lot of components depends on this functionality with data access layer. In moments with peak traffic, we have up to 100 request/second. Database is MySQL or Postgresql.
The question is if someone met real issues with such approach of communication with DBs?
Upvotes: 0
Views: 32
Answers (0)
Related Questions
- Git branch rolling back unchanged files after push force
- Modified files in a git branch are spilling over into another branch
- Git push is deleting branches
- Git revert and reset : Files in the repository are not getting rolled back
- cannot git push due to unrelated upstream file changes
- Git push new branch with same files, uploads all files again
- Git overwrite certain files with every pull/push
- Files deleted with git filter-branch reappear after push and pull back
- Files missing in Gitlab after push
- git push overwrote my changes