I'm actually in the process of moving a large monolith from EC2 to Heroku and this is exactly what the plan is: our DB (> 10TB) is on RDS; ES, Redis also are from AWS. Third-party services aren't provisioned through the marketplace, instead straight through the vendor. Right now this is Datadog and a bug reporter.
We're extremely overprovisioned on EC2 as it is (peaking at 54GB consumed RAM over the last 12 months, and we have 386GB available) so management is welcoming the change to a bunch of Performance L dynos!
We're moving to Heroku for a variety of reasons — least of which is their recent fiasco — primarily dev exp and Pipelines/review apps (still supported!). Both will give our developers a vastly superior experience to what they had: nothing (we desperately need it).
Nobody ever got fired for hiring IBM but I think people may get fired now a days for moving to heroku! Good luck! I would love to hear an update in 12 months if you are still there / heroku is still running.
Previously a senior software engineer at AngelList. Before that I was leading a YC company. Rails contributor with over 10-years experience in the framework leading teams/staff eng/senior eng. Ruby is my home. Serial founder with one big hit and lots of Incredible Journey posts. I’m a joy to work with and am currently very affordable.
Technologies: Ruby on Rails, Ruby without Rails, HTML, CSS, JavaScript, React, Vue, Stimulus
Email: hotlinking@protonmail.com
Previously a senior engineer at AngelList. Before that I was leading a YC company. I’ve single-handedly upgraded Rails versions for apps that are poorly-tested and massive, and well-tested and massive. I’m very product-minded, too.
I’ve recently run into a bit of trouble and could really use some work. I’m available affordably and promptly. Lots of references available.
I have found that the more excited that a customer is excited about a product the more apt they are to be your best salesperson. This was especially true for
one of my consumer SaaS.
Really interesting and I have no idea why it has to be this hard. Fun nonetheless, though cynically, I was holding out hope that hope that after all the work he'd find the feature in the web interface.
We're extremely overprovisioned on EC2 as it is (peaking at 54GB consumed RAM over the last 12 months, and we have 386GB available) so management is welcoming the change to a bunch of Performance L dynos!
We're moving to Heroku for a variety of reasons — least of which is their recent fiasco — primarily dev exp and Pipelines/review apps (still supported!). Both will give our developers a vastly superior experience to what they had: nothing (we desperately need it).