Heroku Is Currently Down
dashboard.heroku.com
dashboard.heroku.com
Still, they're not immune to these types of outages - I believe they're dependent on Google Could but are moving towards running their own data centers at some point. But so far, uptime has been great for us.
Fly.io also looks promising; keeping an eye on that one.
Fly.io's pricing page seems impenetrable to me... I just checked out Render.com and it looks so easy to understand.
I've been wanting to run a Node backend API thing but can't figure out where to put it... been using Cloudflare workers but it kept timing out (going over 10s). Will definitely check out Render's services and $1/mo crons.
How is render for static sites? Do they make you build the site with them or is it a simple "here's an NPM package that github actions can consume".
One of the biggest appeals to me is their simplified, docker-compose like approach to infrastructure as code. Even if I only have a few services, dbs, etc. I still like to have it as code under version control, but things like Pulumi or Terraform are way overkill https://render.com/docs/blueprint-spec
There are still various quality of life improvements I'd like to see, but to me they are on a very attractive path
Thanks so much for pointing it out.
Maybe it is less about new/improved features, I strongly prefer a focused product over one that tries to fulfill everyones whims, but more about guidance on for example for a small team what you think is the “best” way for them to integrate render.com into their dev workflows with typical stacks. How to solve the most common needs and what kind of things are out of scope for render to solve and what could be used instead. For an opinionated tool, it could be a bit clearer, what its opinions are. I think lot the information is already there, but it is quite scattered around between docs, feature request pages and forums.
Specifically related to this AWS outage, Render can already transparently shift your app between AZs, and we're also working on moving services across underlying cloud providers (GCP/AWS and eventually bare metal).
I don't understand much in cloud devops, I just judge from recurring HN comments saying left and right "your startup should have configured up multiple AZ" when some AWS region is down.
Edit: maybe the dashboard is just back up and I don’t see it down.
Getting geographic failover to work seamlessly generally requires application-level knowledge or at the very least, exotic datastores like DynamoDB or Firebase. For better or worse, that's just not the way most people want to develop.
If not, you have a major consistency issue during failover. Maybe your workload can accept dropping a window of transactions, maybe not.
I think you may have been thinking of multi-region, since you mentioned geographic failover. Multi-AZ isn't really geographic failover.
And we will reply with the obvious response, "run your status page on different infrastructure".
Edit: status page updated
Edit: all my apps are in the EU region, which is eu-west-1 (Ireland)
All our monitor are green, but we did experience a bit of increased latency for about 30 minutes.