-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
I have a question regarding connection pools with PostgreSQL. Just recently I set up a DigitalOcean managed database cluster. Prior to setting up my DigitalOcean managed database cluster I was just using a local PostgreSQL database with my Next.js web application. I was using the node-postgres (https://node-postgres.com/) package to create a connection pool. I would create one connection pool instance and import that instance into my serverless functions to query the database. However, with the DigitalOcean managed database cluster it is recommended to use the built-in connection pool tool which uses PgBouncer according to documentation (https://docs.digitalocean.com/products/databases/postgresql/how-to/manage-connection-pools/). If I use the connection pool offered through DigitalOcean should I not use a connection pool through node-postgres? Currently I have a connection pool set up through node-postgres in my Next.js web application and a connection pool set up through DigitalOcean. I am not sure if this “double pooling” is bad practice or will cause issues. I assume if it is bad practice that I should use DigitalOcean's connection pool rather than my node-postgres connection pool? Thanks and let me know if I need to provide more info.