5 ms·
> I can’t see any valid reason not to use Postgres at the back end From TFA: > if you don’t need the Postgres features, they’re a liability. For example, even
by bambax 3y ago
> I can’t see any valid reason not to use Postgres at the back end
From TFA:
> if you don’t need the Postgres features, they’re a liability. For example, even if you don’t use multiple user accounts, you’ll still need to configure and debug host-based authentication. You have to firewall off your Postgres server. And more features mean more documentation, which makes it difficult to understand the software you’re running. The documentation for Postgres 14 is nearly 3,000 pages.
- andrewstuart 3y ago>> you’ll still need to configure and debug host-based authentication. False >> you have to firewall off your server Well yes. Are you saying SQLite servers don’t need a firewall? >> more features/more documentation/hard to understand your software Features lead to powerful software, documentation leads to understanding.
- bambax 3y ago> Are you saying SQLite servers don’t need a firewall I'm not the author. But I can tell you there are no "SQLite servers". That's kind of the whole point.
- voganmother42 3y agothem citing the (excellent) Postgres documentation page count is hilarious. There is a really useful comparison to be made re: features / scope -- but approximating that and punishing a project for how comprehensive their docs are...feels like lines of code as a productivity measure but like 10x less accurate or useful lol
- benbjohnson 3y agoAuthor here. My goal in the comparison was only in terms of scope, not that Postgres folks should be penalized for having good documentation. I think Postgres is great and it makes sense to use it when it's called for. But I think it can be overkill for many projects.
- voganmother42 3y agoMakes sense and I enjoyed the article. Estimating the complexity of using a project can be really...complex. I think about systems I have used which make it easy to use a minimal set of features and where I don't have to reason about or be negatively impacted by aspects I do not benefit from, and other systems where things are less easily isolated and more challenging to reason about. I do think the Postgres docs in particular seek to be a reference in addition to an operating manual and I for one really enjoy them. I think the point is well made that Postgres can be too much (or too much right now) for many projects.