This is super cool - curious about the design decision to go with something like PostgreSQL rather than something like a local SQLite db since I associate that more with ephemeral data
Easy answer - Postgres for everything
No compromises!
A few reasons why:
SQLite is local, Postgres can be available remotely, independent of where your application is running
Postgres has a richer ecosystem for things like vector, time-series, geospatial, full text search, etc than SQLite
Ghost makes Postgres feel as lightweight as SQLite
(And we also happen to love Postgres)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is super cool - curious about the design decision to go with something like PostgreSQL rather than something like a local SQLite db since I associate that more with ephemeral data
Easy answer - Postgres for everything
No compromises!
A few reasons why:
SQLite is local, Postgres can be available remotely, independent of where your application is running
Postgres has a richer ecosystem for things like vector, time-series, geospatial, full text search, etc than SQLite
Ghost makes Postgres feel as lightweight as SQLite
(And we also happen to love Postgres)