I use postgres for very simple apps. I have a Dockerfile I use in my boilerplate repo. It takes a single make cmd for me to build, start and run migrations. Its as simple as using sqlite.

▲

turtlebits 3 hours ago | parent | next [-]

Its 2x the infra. You have to manage an additional process, auth, backups, logging, etc.

▲

tasuki 4 hours ago | parent | prev [-]

But now you have another process to babysit. How do you keep it healthy? And you have to ensure the client-server communication won't break.

For me the main benefit of sqlite is that it's a library rather than an app.

▲

not_kurt_godel an hour ago | parent | next [-]

> But now you have another process to babysit. How do you keep it healthy?

I've been assured by many HN users that running apps/sites on a single VPS requires near-zero maintenance or monitoring to achieve acceptable uptime 24/7/365 for years on end, sooooo...just pretend it will never fail like your main server process?

▲

ai_fry_ur_brain 41 minutes ago | parent | next [-]

Ive been assured by many HN users that you must have 24/7/365 uptime for everything in case one of your 10 bi-monthly users decides to log on.

▲

bdangubic 29 minutes ago | parent | prev [-]

24/7/365 is needed (or achieved) just about never. our big tech is proving 90% will soon be utopia as well. being down has always been fine for 99.999975% of all projects on the planet.

	▲	not_kurt_godel a minute ago \| parent [-]
		Ok, now tell me the stat by percentage of overall market revenue rather than project count

▲

ai_fry_ur_brain 4 hours ago | parent | prev [-]

I have boilerplate for client-server communication that makes it pretty trivial to build on top of.

Im not saying that sqlite isn't useful, im mostly saying that using postgres doesnt have to be complicated.