Thanks for the valuable feedback. As an engineer, I see what you're saying. I need to get back on track with my "Database Internals" series. Already have a few ideas in the backlog. Stay tuned, my friend! Btw, is there anything specific you'd like to learn more about from the database world (by looking into how things work internally)?
@@DevMastersDb well... One thing that I find interesting is commits, rollbacks and eventual consistency. Indexes as well, how they work behind the scenes. I know some theory, but actually seeing it would be cool. Also, it would be interesting to improve performance of a slow system, something like that.
Glad you found it helpful! Thanks for dropping the note. Well, there is no magic number for the connection pool size. Usually, connection pools cache 5-10 connections by default (that's exactly what I used in my app). Some folks pick a number between 10-30. But, a good engineering approach would be to measure various metrics (throughput, number of concurrent connections, number of CPUs) and set a pool size accordingly. Take a look at this discussion: stackoverflow.com/questions/8753442/thinking-behind-decision-of-database-connection-pool-size
have a question about Docker. I'm trying to run Docker Compose for two services: a PostgreSQL database and a Next.js application. The database is initialized with several million rows, so many insert operations are executed when it's run. The Next.js application needs access to the database at build time. How can I ensure that one service waits for the database to be ready? I've tried writing health checks, but they didn't work out. Do you have any tips or perhaps a video that could help? I would greatly appreciate it.
Hey, I usually use the wait-for-it script. It might not be the best solution but it works like a charm for me: github.com/vishnubob/wait-for-it Check this article that shows how to use the script from Docker: laurent-bel.medium.com/waiting-for-postgresql-to-start-in-docker-compose-c72271b3c74a Let me know if it works for you. I'll consider recording a video.
This was awesome. I miss videos like this, where they show you in practice what is happening. Thank you for it.
Thanks for the valuable feedback. As an engineer, I see what you're saying. I need to get back on track with my "Database Internals" series. Already have a few ideas in the backlog. Stay tuned, my friend!
Btw, is there anything specific you'd like to learn more about from the database world (by looking into how things work internally)?
@@DevMastersDb well... One thing that I find interesting is commits, rollbacks and eventual consistency. Indexes as well, how they work behind the scenes. I know some theory, but actually seeing it would be cool.
Also, it would be interesting to improve performance of a slow system, something like that.
@@necrotikS noted!
great content !
Thanks, glad you liked it!
Thanks a lot
you're welcome, I'm glad you like the video!
thanks a lot for this video !
Glad you liked it!
Thanks for the video. It was very helpful information. But what is the proper pool size when you set up the connection pool ?
Glad you found it helpful! Thanks for dropping the note.
Well, there is no magic number for the connection pool size. Usually, connection pools cache 5-10 connections by default (that's exactly what I used in my app). Some folks pick a number between 10-30.
But, a good engineering approach would be to measure various metrics (throughput, number of concurrent connections, number of CPUs) and set a pool size accordingly. Take a look at this discussion: stackoverflow.com/questions/8753442/thinking-behind-decision-of-database-connection-pool-size
have a question about Docker. I'm trying to run Docker Compose for two services: a PostgreSQL database and a Next.js application. The database is initialized with several million rows, so many insert operations are executed when it's run. The Next.js application needs access to the database at build time. How can I ensure that one service waits for the database to be ready? I've tried writing health checks, but they didn't work out.
Do you have any tips or perhaps a video that could help?
I would greatly appreciate it.
Hey, I usually use the wait-for-it script. It might not be the best solution but it works like a charm for me: github.com/vishnubob/wait-for-it
Check this article that shows how to use the script from Docker: laurent-bel.medium.com/waiting-for-postgresql-to-start-in-docker-compose-c72271b3c74a
Let me know if it works for you. I'll consider recording a video.