For many teams, Heroku is still a feasible starting point, as it should: it provides an outstanding developer experience, which allows you to bring a MVP live really fast. You do not need to worry about hiring an ops team or managing your infrastructure.
Latest when it comes to scale however, teams experience some crucial limitations of Heroku: developers can not use technology they love, because it doesn’t integrate with Heroku. You also can’t use the cloud provider of your choice, which might save you considerable expenses, all the while Heroku gets pricier as you grow.
Many teams facing scalability issues consider migrating from Heroku to Kubernetes. Not without risks, this decision should be evaluated carefully.
In this webinar we will talk to Masashi Beheim, Chief of Staff to the SVP Engineering at Forto, who successfully completed this journey. His team migrated from Heroku to Kubernetes, providing them with the technical foundation to scale their Series B Startup.
Topics we will discuss:
- When is the best time to migrate away from Heroku
- How to plan and execute the migration to Kubernetes
- Mistakes you should avoid and pitfalls you might face during the migration process
After a 30 minutes talk, there will be 15 minutes for Q&A.
Audience - who should join?
DevOps Engineers, Site Reliability Engineers, Platform Engineers, System Engineers, Technical Architects, Application Developers with an affinity with DevOps and Technical Management.