[deleted]
I run multiple $10K MRR companies on a $20/month tech stack
51–60 of 539 posts
Re: I run multiple $10K MRR companies on a $20/month tech stack
#52Earlier quoted context omitted.
Why is SQLite bad for production database? Yes, it has some things that behave differently than PostgreSQL but I am curious about why you think that.
For read only it can be a great option. But even then I would choose D1 which has an amazing free tier and is sqlite under da hood.
But then you don't get the benefits of having the DB locally, with in-process access.
Re: I run multiple $10K MRR companies on a $20/month tech stack
#53You can get all the advantages and almost none of the constraints by buying a bigger base server for $50/m
Re: I run multiple $10K MRR companies on a $20/month tech stack
#54If you can’t articulate what you need funding for, don’t be surprised if nobody will give it to you?
Re: I run multiple $10K MRR companies on a $20/month tech stack
#55Just in case, if there are others like me who where wondering what does "MRR" means, it seems to be "monthly recurring revenue".
I'm just curious but is it the case that you signed up here 16 years ago and you didn't know what MRR means?
Obviously they are lacking the sigma hustle grindset.
Its like not having syphilis or cancer, its a good thing.
Re: I run multiple $10K MRR companies on a $20/month tech stack
#56I learned nothing. Most of this seems like common basic advice, wrapped up in AI written paragraphs... Initially from the title, I thought it would be about brainstorming and launching a successful idea, and that sort of thing.
If you feel like it: start a blog! You have knowledge that you consider basic and a certain other subset of the population is interested in it and doesn't know it exists.
Re: I run multiple $10K MRR companies on a $20/month tech stack
#57> The enterprise mindset dictates that you need an out-of-process database server. But the truth is, a local SQLite file communicating over the C-interface or memory is orders of magnitude faster than making a TCP network hop to a remote Postgres server. I don't want to diss SQLite because it is awesome and more than adequate for many/most web apps but you can connect to Postgres (or any DB really) on localhost over…
> It's not much harder to use than SQLite, you get all of the Postgres features, it's easier to run reports or whatever on the live db from a different box, and much easier if it comes time to setup a read replica, HA, or run the DB on a different box from the app.
Isn't this idea to spend a bit more effort and overhead to get YAGNI features exactly what TFA argues against?
Re: I run multiple $10K MRR companies on a $20/month tech stack
#58Re: I run multiple $10K MRR companies on a $20/month tech stack
#59I read it as an article in defence of boring tech with a fancier/clickbaity title. Here’s the more honest one i wrote a while back: https://aazar.me/posts/in-defense-of-boring-technology
While I agree with your points, this one could be more nuanced:
> Infrastructure: Bare Server > Containers > Kubernetes
The problem with recommending a bare server first is that bare metal fails. Usually every couple of years a component fails - a PSU, a controller, a drive. Also, a bare metal server is more expensive than VPS.
Paradoxically, a k3s distro with 3 small nodes and a load balancer at Hetzner may cost you less than a bare metal server and will definitely give you much better availability in the long run, albeit with less performance for the same money.
Re: I run multiple $10K MRR companies on a $20/month tech stack
#60Nice list! I'd say the SQLite with WAL is the biggest money saver mentioned. One note: you can absolutely use Python or Node just as well as Go. There's Hetzner that offers 4GB RAM, 10TB network (then 1$/TB egress), 2CPUs machines for 5$. Two disclaimers for VPS: If you're using a dedicated server instead of a cloud server, just don't forget to backup DB to a Storage box often (3$ /mo for 1TB, use rsync). It's a good…
> Nice list! I'd say the SQLite with WAL is the biggest money saver mentioned. Funny you said that. I migrated an old, Django web site to a slightly more modern architecture (docker compose with uvicorn instead of bare metal uWSGI) the other day, and while doing that I noticed that it doesn't need PostgreSQL at all. The old server had it already installed, so it was the lazy choice. I just dumped all data and loaded…
Yep, it literally is a one-file backup. And runtime it's so much faster for apps where write serialisation is acceptable.