[danslo]

s/postgres/sqlite/g

[hshdhdhehd]

Postgres is simpler. Get your cloud to manage it. Click to create instance, get failover with zero setup. Click button 2 to get guaranteed backups and snapshot point in time.

[1718627440]

When you use sqlite, you can distribute your program by distributing a single executable file. That's what I call simple.

[Komte]

Don't agree. Getting managed postgress from one of the myriad providers is not much harder than using sqlite, but postgress is more flexible and future proof.

[eskibars]

Isn't the entire point of this post that many companies opt for flexible+future proof far too prematurely?

[ErroneousBosh]

I use Postgres for pretty much everything once I get beyond "text in a database with a foreign key to a couple of things".

Why?

Because in 1999 when I started using PHP3 to write websites, I couldn't get MySQL to work properly and Postgres was harder but had better documentation.

It's ridiculous spinning up something as "industrial strength" as Postgres for a daft wee blog, just as ridiculous as using a 500bhp Scania V8 for your lawnmower.

Now if you'll excuse me, I have to go and spend ten seconds cutting my lawn.

[StarGrit]

ORMs have better support I've found in the past (at least in .NET and Go) for Postgres. Especially around date types, UUIDs and JSON fields IIRC.

[Hendrikto]

You don’t need an ORM either. It’s just another level of complexity for very little to no gain in almost all cases. Just write SQL.

[rcarmo]

This. So much this. Of course, at one point you start wanting to do queues, and concurrent jobs, and not even WAL mode and a single writer approach can cut it, but if you've reached that point then usually you a) are in that "this is a good problem to have" scalability curve, and b) you can just switch to Postgres.

I've built pretty scalable things using nothing but Python, Celery and Postgres (that usually started as asyncio queues and sqlite).

[forgetfulness]

A queue and a database are more shots on the architecture golf though.

[anonzzzies]

Yeah, we run a fairly busy systems on sqlite + litestream. It's not a big deal if they ae down for a bit (never happened though) so they don't need failover and we never had issues (after some sqlite pragma and BUSY code tweaking). Vastly simpler than running + maintaining postgres/mysql. Of course, everything has it's place and we run those too, but just saying that not many people/companies need them really. (Also considering that we see system which DO have postgres/mysql/oracle/mssql set up in HA and still go down for hours do a day per year anyway so what's it all good for).

[sachahjkl]

back in the day, the hype was all arround postgres, but I agree