Nicholas C. ZakasYou’re building a webapp consisting of a Node.js app, a database, a queue, and a worker.
To which cloud platform to do deploy it?
tea 🌺
Kevin Stewart@kstewart fair point. Might revisit in 2024.
Brandon Mills@nzakas depends. Side project or work project? If work and reliability matters, AWS because I’m already familiar with that and I can offload all the non-JS things I don’t know deeply. RDS PostgreSQL for the database. Queue in the DB, Redis, or SQS in increasing order of scale. ECS for Node and possibly worker. If low-budget side project and downtime is just “oh, I guess I get to learn something new this weekend”, might cram it all into a single VM on DigitalOcean and roll my own everything.
@nzakas re queueing in the DB, I’ve been using something similar to https://adriano.fyi/posts/2023-09-24-choose-postgres-queue-technology/ for years without issue. I only need it to handle tens of entries per minute, and I have one less dependency. If I needed fancier features, I’d use something else, but for simple FIFO, at-least-once delivery, it’s done the trick.
Choose Postgres queue technology
Introduction Postgres queue tech is a thing of beauty, but far from mainstream. Its relative obscurity is partially attributable to the cargo cult of “scale”. The scalability cult has decreed that there are several queue technologies with greater “scalability” than Postgres, and for that reason alone, Postgres isn’t suitably scalable for anyone’s queuing needs. The cult of scalability would rather we build applications that scale beyond our wildest dreams than applications that meet concrete customer and business needs. Postgres’ operational simplicity be damned; scale first, operate later.
Sjors Rijsdam@nzakas AWS using @enhance_dev
Brett Peary@nzakas I might try this https://www.flightcontrol.dev/
