2 ms·
I am sure MySQL is a great fit for your use case. For others reading your comment though, I did want to list some things I have used with Postgres that relate
by gshulegaard 6y ago
I am sure MySQL is a great fit for your use case.
For others reading your comment though, I did want to list some things I have used with Postgres that relate to connection pooling and data partitioning:
* PGBouncer for connection pooling/sharing.
* Postgres Table Inheritance for table partitioning (https://www.postgresql.org/docs/12/ddl-inherit.html https://www.postgresql.org/docs/12/ddl-inherit.html)
* PGPartman for automating the creation of partitions (https://github.com/pgpartman/pg_partman https://github.com/pgpartman/pg_partman)
* Citus for low-barrier data sharding (it's a Postgres Extension like PostGIS) (https://www.citusdata.com/ https://www.citusdata.com/)