531–539 of 539 posts
Earlier quoted context omitted.
Yes but there is still a (small) window where confirmed writes can be lost
Right and that window is bigger for RDS by the looks of it.
Is suppose the difference is RDS has high 9s, whereas in the Litestream case the frequency of crashes is tied to your application code and deployment process. In practice this will take more work to reach the same uptime?
This is supposed to be a contrarian opinion yet this is a retoric yapped non-stop in the “build in public” community. Of course lean is a good approach, it makes sense, and most engineers know this. Is not a new concept, we’ve been doing this for years in every branch of engineering. The invented “people start with a k8s cluster for 5 users” doesn’t really exist. This is just a story repeated ad nauseam to fit a narr…
I've seen A LOT of public sector projects starting out with loads of Azure services and >$3000 montly bills for applications that could've easily run on a single VM.
Companies cargo culting Big Data stacks when their data is nowhere near big is very prevalent.
Earlier quoted context omitted.
Interesting comparison. Have you done one for sqlite vs H2? Since you're using clojure, it seems a natural fit. According to what I've read, H2 is faster than sqlite, but it would be interesting to see some up to date numbers on it.
That's a good point. I'll give that a go and do a write up at some point. The choice to use SQLite for me isn't actually about speed (LMDB is way faster). I just get tired of people saying switch to Postgres for speed/scale. Postgres is great for many things but speed/scale is not its strength. The main reason I use SQLite is the affordances and conveniences of an embedded database. Being able to easily have many dat…
This is similar to what I do. Linode, Debian, Go, HTMX, SQLite (with modernc.org/SQLite so I have no CGO dependency) and Caddy. If I have apps that need a lot of storage, I just add an S3 bucket.
That’s neat. How do you handle the rest: - backups - upgrades to the os packages (and downtime from reboots) - updates to container images (if you run any) - monitoring and alerting (logs, http 500 increase, http 200 drop, etc) Asking because I’m looking for pointers on how to solve this myself when deploying to a VPS rather than AWS alphabet soup or a PaaS
Earlier quoted context omitted.
Apparently the phrase cargo cult software engineering is not common anymore. Explains these things perfectly.
I end up explaining this term to every junior developer that doesn't know it sooner or later, the same way I explain bike shedding to all PMs that don't know it... often sooner, rather than later. It seems to really help if you can put a term to it.
It’s sad this whole group of people only respond to what amounts to filler slide deck material. Defined business vocabulary, acronyms, etc.
Earlier quoted context omitted.
It's like the old Herman cartoon - "Sure I could sell it to you for $50, but wouldn't you rather have a $5,000 painting?" People often don't like admitting that their project does not require a rocket and the associated scientists. Often even Kubernetes and friends is a bridge too far for what is realistically a single-page PHP app.
The other factor is 'not my money' syndrome. People who work at companies and don't have a real stake often don't feel bad about burning it for the sake of convenience.
If this sounds like basic advice, consider there are a lot of people out there that believe they have to start with serverless, kubernetes, fleets of servers, planet-scale databases, multi-zone high-availability setups, and many other "best practices". Saying "you can just run things on a cheap VPS" sounds amateurish: people are immediately out with "Yeah but scaling", "Yeah but high availability", "Yeah but backups"…
Its worse than that. Thats how they are taught, and shamed if they dont "enterprise" their hello world app with 20 layers of failsafes...
Earlier quoted context omitted.
That's a good point. I'll give that a go and do a write up at some point. The choice to use SQLite for me isn't actually about speed (LMDB is way faster). I just get tired of people saying switch to Postgres for speed/scale. Postgres is great for many things but speed/scale is not its strength. The main reason I use SQLite is the affordances and conveniences of an embedded database. Being able to easily have many dat…
I haven't tried sqlite because the lack of data types is off putting to me. I want to like derby because they have gone to the trouble of making their database JPMS modular. But derby doesn't have UUID types and I want UUID types. Especially with Java 26 adding UUIDv7. I end up on H2 as a result.