Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SQLite the only database you will ever need in most cases (2021)

unixsheikh.com

Post reply on HN
Print view View original

201–210 of 378 posts

Re: SQLite the only database you will ever need in most cases (2021)

#201

Post by justinclift »

bogwog wrote: post #86
irskep wrote: post #29

This sentiment pops up regularly on HN, and I've seen at least one article per month for the past few months, but the trouble is, none of them seem to help you actually deploy it. They assume you're comfortable spinning up public web servers. If you want to use a PaaS to deploy an app, because you don't want to spend your time learning to be a sysadmin, then all the tutorials are going to put you on the Postgres path…

> I'm an application developer and I do not want to become a release engineer. I resent even having to learn Docker. :-) Sorry, but that's a terrible attitude to have. You don't need to be a full-blown sysadmin to know how to do basic deployments, and learning these things will make you a better developer.

At the same time, I kind of wonder at the direction of things when pretty much every package and application has decided to embrace becoming more complex over time.

It's only going to increase cognitive load, potentially without end (?) which doesn't sound wise long term. :(

Re: SQLite the only database you will ever need in most cases (2021)

#202

Post by canadianfella »

erik_seaberg wrote: post #173
canadianfella wrote: post #122

Earlier quoted context omitted.

Why do people use hosted databases instead of just installing them? I don’t understand it.

If you install your own copy, you are on call for it, and the colo is unlikely to offer much help. You also have to set up monitoring or you won’t even know when it fails. Then there’s replication. Backups. All this stuff is work that PaaS vendors are ready to automate away, if my time is expensive for the org. For fun, sure, dink around and learn as long as there are no customers to affect.

Can’t you just run a script that sets all that up for you? Just like any other programming task?

Re: SQLite the only database you will ever need in most cases (2021)

#204

Post by ospider »

erulabs wrote: post #45

See I’ve been using Vitess on Kubernetes for even personal projects and I gotta say I love that I can run, for 10 bucks a month on Linode, the same tools that I know by experience I can scale to a multi-billion dollar valuation worth of customers. Heck I even run it in development on my laptop thanks to Skaffold. Sure it’s all insane overkill - but I use Linux for the same reasons - I want one API that I can use ever…

AFAIK, you can only buy 2 smallest nodes with $10 on Linode, how do you create a k8s cluster with that?

Re: SQLite the only database you will ever need in most cases (2021)

#205

Post by justinclift »

stirfish wrote: post #183
irskep wrote: post #148

Earlier quoted context omitted.

I really appreciate you taking the time to respond with these details. I do go deep on application-level tech (CSS, HTML, JS with and without frameworks, iOS dev, etc) and it's always disheartening for people to claim that choosing not to focus on specific technologies makes you a worse human being. The other thing that's going completely over people's heads here is that I made this repo with the intent of helping ot…

>choosing not to focus on specific technologies makes you a worse human being. maybe that'll make you a worse engineer, but engineers are not human beings.

> engineers are not human beings

That's funny, all the engineers I've known have been.

What crowd have you been hanging out with? :)

Re: SQLite the only database you will ever need in most cases (2021)

#207

Post by Kranar »

stirfish wrote: post #183
irskep wrote: post #148

Earlier quoted context omitted.

I really appreciate you taking the time to respond with these details. I do go deep on application-level tech (CSS, HTML, JS with and without frameworks, iOS dev, etc) and it's always disheartening for people to claim that choosing not to focus on specific technologies makes you a worse human being. The other thing that's going completely over people's heads here is that I made this repo with the intent of helping ot…

>choosing not to focus on specific technologies makes you a worse human being. maybe that'll make you a worse engineer, but engineers are not human beings.

Don't know what version of Chat-GPT you're using, but last I checked engineers are still human.

Re: SQLite the only database you will ever need in most cases (2021)

#208

Post by noisenotsignal »

irskep wrote: post #29

This sentiment pops up regularly on HN, and I've seen at least one article per month for the past few months, but the trouble is, none of them seem to help you actually deploy it. They assume you're comfortable spinning up public web servers. If you want to use a PaaS to deploy an app, because you don't want to spend your time learning to be a sysadmin, then all the tutorials are going to put you on the Postgres path…

This is cool to see! I’ve been working on a website for online ordering, and a key requirement is free hosting [0]. After some searching I figured fly.io + SQLite would be enough for my use case but I can’t be 100% sure until I actually deploy, which I haven’t yet. It’s nice to know someone else has done it this way successfully!

[0] - It’s for a small business not in the US with no serious requirements on availability etc so free, or close to it, seems achievable.

Re: SQLite the only database you will ever need in most cases (2021)

#210

Post by joshspankit »

drexlspivey wrote: post #162
joshspankit wrote: post #156

I’ve argued this before and I’ll argue it here now: Modern computers are fast enough that in many cases “the only database you will ever need” can be files on the filesystem. For example “1 row = 1 file”. It brings additional benefits as well: for low-write applications you can use git to get a history (+transactions if you store them in the log), backups are super easy, replication is trivial. For higher-write appli…

how do you do joins?

Use filename as your primary key and folder structure as “table”

Though, if you are doing a lot of joins your application is probably a better fit for a graph database instead of a “relational” one anyway

Post reply on HN