Re:MRSK vs. Fly.io
by bkazez on Thursday March 23, 2023 @03:33AM
(#35271534)
Exactly. It's like using InDesign to make a shopping list with gorgeous kerning and ligatures. Is it necessary? No. Does it use more than 1% of InDesign's power? No. Is it fun to learn a pro tool? Yes. Will it scale infinitely to whatever you'll need in the future? For sure.
For a small Rails side project, managed Kubernetes + Helm gives:
1. True zero-downtime deploys - no suspending of requests like Heroku or MRSK.
2. Reassurance that you can scale up someday without spending $50/mo on tiny Heroku dynos.
3. Reassurance that you can add services (e.g. Redis/sidekiq, once you need it) without expensive Heroku add-ons that eventually get discontinued.
3. Stability of building on infrastructure that is being used to run enormous production sites.
4. Minimal complexity. It took some time to learn the abstractions, but for a simple setup like mine, it's not complicated.
5. Minimal vendor lock-in. For a side project, "I spent a few hours clicking the right buttons on a GUI console" is vendor lock-in. So is YAML, but I can take it to any vendor.
6. Maximal longevity. I don't want to switch infrastructures every year as startups (or Heroku...) come and go. I have some GKE-specific code in my YAML (database authentication + a few lines of "use Spot VMs for staging" + static IPs), but it's minimal.
For a small Rails side project, managed Kubernetes + Helm gives:
1. True zero-downtime deploys - no suspending of requests like Heroku or MRSK. 2. Reassurance that you can scale up someday without spending $50/mo on tiny Heroku dynos. 3. Reassurance that you can add services (e.g. Redis/sidekiq, once you need it) without expensive Heroku add-ons that eventually get discontinued. 3. Stability of building on infrastructure that is being used to run enormous production sites. 4. Minimal complexity. It took some time to learn the abstractions, but for a simple setup like mine, it's not complicated. 5. Minimal vendor lock-in. For a side project, "I spent a few hours clicking the right buttons on a GUI console" is vendor lock-in. So is YAML, but I can take it to any vendor. 6. Maximal longevity. I don't want to switch infrastructures every year as startups (or Heroku...) come and go. I have some GKE-specific code in my YAML (database authentication + a few lines of "use Spot VMs for staging" + static IPs), but it's minimal.