You don't need your database on a dedicated server. Not sure why the comparison table claims "$30 + DB server" when your web server is a perfectly good server already.
Presumably to remove it from the need to calculate. Everyone is using a different approach and one DB may require a lot more than the 30$ server can provide.
The claim is presumably that a web server running SQLite is that much better than a web server running Postgres or Redis. So they end up including it in the calculation anyway but only on one side... so it's just simply not even apples to apples.
I meant a server dedicated to the database, but yes, I agree. Never said the web server had to be bare metal.
I wonder if the misconception is from relying on managed database services. Maybe instead of installing their own database, they order one from a service provider like AWS or GCP. That would explain how they'd think that a database like Postgres would have to live on a different machine.
The goal is to optimize everything other than the database. The vast majority of PHP apps are I/O bound and this webserver lets you handle 100x as many users as php-fpm. That’s the point. Your code can remain the same and keep using whatever database.
LoganDark · · focus · HN ↗
iinnPP · · focus · HN ↗
Now everyone can understand the math.
LoganDark · · focus · HN ↗
conductr · · focus · HN ↗
LoganDark · · focus · HN ↗
I wonder if the misconception is from relying on managed database services. Maybe instead of installing their own database, they order one from a service provider like AWS or GCP. That would explain how they'd think that a database like Postgres would have to live on a different machine.
EGreg · · focus · HN ↗