3 ms·
For a Saas maintained by one person, would you recommend MySQL or Postgres? I don’t know yet the volume of users or connections I will receive (perhaps zero?),
by tkiolp4 5y ago
For a Saas maintained by one person, would you recommend MySQL or Postgres? I don’t know yet the volume of users or connections I will receive (perhaps zero?), but I do like to keep things simple (this pgbouncer thing one may need with postgres makes me feel uncomfortable).
- funcDropShadow 5y agoI would use always start with Postgres, because of its vast flexibility and extremely solid feature set, not to forget the excellent docomentation. I'v used Postgres in numerous projects and never had the need for pg_bouncer. Although I am sure there are some situation where it might be beneficial to use it. E.g. on the JVM it is best practice since 20 years to always use a connection pool in front of all JDBC drivers. IMHO transactional DDL is the killer feature for a fast moving project with customers.
- mst 5y agoPossibly heretical view: SQLite (with foreign keys) and WAL mode for concurrent writers and filesystem snapshots for backup. Do that until you can't, that way you'll actually have some idea where your database is going before you pick an actual server.