471–480 of 539 posts
Earlier quoted context omitted.
And now big tech often doesn't even have the high availability to show for all that complexity.
Remember if you ever feel disappointed, the king of scale Google playstore updates stats once a day
Earlier quoted context omitted.
An interactive transaction works like this in pseudo code. beginTx // query to get some data (network hop) result = exec(query1) // application code that needs to run in the application safeResult = transformAndValidate(result) // query to write the data (network hop) exec(query2, safeResult) endTx How would you batch this in postgres and get any value? You can nest them all in a single transaction. But, because they…
> How would you batch this in postgres and get any value? You can nest them all in a single transaction. But, because they are interactive transactions that doesn't reduce your number of network hops. you can write it as stored procedure in your favorite language, or use domain socket where communication happens using through shared memory buffs without network involved. In your post, I think big performance hit for…
When did postgres add PL/Lisp support?
There are zero reasons to limit yourself to 1GB of RAM. By paying $20 instead of $5 you can get at least 8gb of RAM. You can use it for caches or a database that supports concurrent writes. The $15 difference won’t make any financial difference if you are trying to run a small business. Thinking about on how to fit everything on a $5 VPS does not help your business.
Earlier quoted context omitted.
Sqlite smokes postgres on the same machine even with domain sockets [1]. This is before you get into using multiple sqlite database. What features postgres offers over sqlite in the context of running on a single machine with a monolithic app? Application functions [2] means you can extend it however you need with the same language you use to build your application. It also has a much better backup and replication st…
> What features postgres offers over sqlite in the context of running on a single machine with a monolithic app The same thing SQL itself buys you: flexibility for unforeseen use cases and growth. Your SQLite benchmark is based in having just one write connection for SQLite but all eight writable connections for Postgres. Even in the context of a single app, not everyone wants to be tied down that way, particularly w…
Earlier quoted context omitted.
It is better to keep it simple and rework as needed than to try to anticipate everything ahead of time.
I'm not anticipating everything ahead of time, I'm choosing mature tech that does what I need and then some. There's no misstep there. The real problem I've seen with choosing software tech is "new, shiny".
That choice is what tends towards a"minimum prod deployment" consisting of something like a pair of app servers behind a load balance with a pair of redundant databases behind them and usually some sort of object store as well. Assuming you engineer you app and db schemas sanely, you can reliably get four nine out of a setup like that. On AWS that looks like an aELB with two EC2 instances and a multiAZ RDS with a few S3 buckets. At on demand rates with .medium ec2 and rds instances that runs about $150/month - or maybe as low as $100 with reserved instances. You could probably deploy that for $60 or so on something like Linode or Digital ocean.
That's usually fine when you're spending someone else's money, and they're fully-but-incorrectly expecting their idea to need Netflix or Facebook scale within six months.
|||||If it's _my_ money, something "less scalable" that runs closer to $20/month that will easily support enough traffic to prove product market fit and generate enough sales/profit to suppot both otself and a team to rebuikd it when/if it ever needs it is a really sensibly approach.
SQLite is fine, but I have ran Postgresql on a $20 server without any issues, and I would suggest if you have to deal with concurrent users and tasks, Postgresql is the way to go. SQLite WAL works, but sometimes it caused some issues, when you have a lot of concurrent tasks running continuously. And, not sure I'm correct, but I felt Postgresql has more optimized storage if you have large text data than SQLite, at lea…
Earlier quoted context omitted.
> How would you batch this in postgres and get any value? You can nest them all in a single transaction. But, because they are interactive transactions that doesn't reduce your number of network hops. you can write it as stored procedure in your favorite language, or use domain socket where communication happens using through shared memory buffs without network involved. In your post, I think big performance hit for…
> you can write it as stored procedure in your favorite language When did postgres add PL/Lisp support?
> 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…
Postgres too (though it might come with a few operational headaches)
all these things are awesome.
however the complex over-engineering comes from people putting a k8 cluster or some cloud services when self hosting will do.
Earlier quoted context omitted.
FYI, the color gradient on your website is an easy tell that it was vibe coded: https://prg.sh/ramblings/Why-Your-AI-Keeps-Building-the-Same...
A blog that's 11 years old and uses a minimalist CSS framework https://picocss.com ? It's a static blog that renders markdown... there's literally nothing to code, let alone vibe code.
This is quite the coincidence. Forgive me for assuming your website was built without attention to detail and care.
Earlier quoted context omitted.
Digital ocean has Kubernetes ffs. It's all of five minutes to write a deployment yaml and ingress and have literally anything on the web for a handful of dollars a month. I've written rust services doing 5k QPS on DO's cheapest kube setup. It's not rocket science. Serverless node buns with vite reacts are more complicated than this. Ten lines of static, repeatable, versioned yaml config vs a web based click by click…
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.