3 ms·
If your database is write heavy, and receives a bunch of traffic, then PostgreSQL is probably a better fit. Also, if the SQL that's needed in an application is
by justinclift 4y ago
If your database is write heavy, and receives a bunch of traffic, then PostgreSQL is probably a better fit.
Also, if the SQL that's needed in an application is more "enterprise" style, then SQLite isn't there (yet). ;)
- masklinn 4y agoAlso if you want things like advanced datatypes or indexes, or features sqlite doesn't have (of which there are many, though in the last few years the support for "advanced" SQL has really taken a leap forward making it much more enjoyable).
- vlovich123 4y agoAnyone looking at hand-rolled disks on files isn't needing anything sqlite won't give them. + getting people comfortable with sql & then migrating from sqlite to postgres isn't a bad tradeoff.