51–60 of 63 posts
Earlier quoted context omitted.
We define worth. I mention Heroku as a great way to make web applications at various scales. Reliable, and easy to use.
Heroku was / is like a mainframe. You get provisioning, scaling, configuration, etc all sorted out for you, as long as you pay through the nose.
Earlier quoted context omitted.
We define worth. I mention Heroku as a great way to make web applications at various scales. Reliable, and easy to use.
Heroku was / is like a mainframe. You get provisioning, scaling, configuration, etc all sorted out for you, as long as you pay through the nose.
Earlier quoted context omitted.
You can migrate to the heavier infra later. I am serving hundreds of concurrent users from a single Rust binary backed by Sqlite. So far it hasn't shown the slightest problems and migration can happen if the service grows an order of magnitude (or two) from here.
Migration/upgrades need to happen no matter the size of the service, so I'm not sure what you mean.
Earlier quoted context omitted.
> no downtime except when it restarts for updates. This sounds a little like saying "all of North America except the U.S." I don't think people are worried about random breakdowns on a single VPS, but scheduled updates are still downtime, and downtime causes revenue loss regardless of why it happened. Any time a service is important enough I ask for two servers and a load balancer specifically to handle deployments a…
> upgrade windows Ok, that explains this and the above comment. The last time I had to restart anything to apply an OS update was when I moved to a new RHEL LTS version, the lifespan of which is about 10 years. And there are many ways to do similar GNU/Linux upgrades without a restart at all. Does Windows Server really need to restart for updates like normal Windows? If so, that's hilariously crap and I'm glad I've n…
Yes, you can restart all the services that probably slightly less downtime to full reboot on most VPS these days.
I was shat on multiple times by throbbing-brain architecture guys for this, but what I've done multiple times that worked in prod, was to start with a single monolith with dependency injection, and run all services in the same process. Once the compute and robustness demands mandated we should scale the thing across multiple machines, both horizontally and vertically, I would replace most DI services with proxies tha…
I do this for my personal projects. Rust. Axum. Single compiled binary. Even html/js/css is baked into it via RustEmbed. Sqlite + litestream to S2. Cloudflare in front. Works extremely well.
Earlier quoted context omitted.
Heroku was / is like a mainframe. You get provisioning, scaling, configuration, etc all sorted out for you, as long as you pay through the nose.
So, it's a price issue? My confusion / out-of-the-loop is thus: I hear that Heroku has gone downhill, is no longer recommended etc, yet I've noticed no degradation personally. Works well, is stable, has all the benefits I initially liked it for.
I was shat on multiple times by throbbing-brain architecture guys for this, but what I've done multiple times that worked in prod, was to start with a single monolith with dependency injection, and run all services in the same process. Once the compute and robustness demands mandated we should scale the thing across multiple machines, both horizontally and vertically, I would replace most DI services with proxies tha…
In what programming language did you do this? Sounds like a nice mostly future-proof architecture.
If you like the sound of this, check out Elixir/Phoenix