arrow_back 7 Pitfalls for DevOps in Enterprises
Goblin - Automated Resiliency Testing arrow_forward
Lessons in moving from physical hosts to Mesos
Submitted by Raj Shekhar (@lunatech) on Tuesday, 19 January 2016
This talk is for people who are thinking about the moving to Mesos and will help them understand what to expect and how to do the migration.
t.co is the URL shortening service created by Twitter. As part of scaling up, t.co moved to using Mesos. We saw significant gain is deployment speed, scalability and reduction in operational headaches.
This talk will provide an introduction to Mesos+Aurora, and cover how t.co service migrated from running on physical hardware to Mesos. It will also cover the challenges t.co had during the migration, the “gotchas” and debugging techniques for uncovering performance issues.
- Introduction to Mesos + Aurora - Benefits of moving to Mesos - Migration steps for moving from t.co to Mesos - Challenges faced and how t.co overcame them
I have been working as a site reliability engineer since 2005, first at Yahoo! and currently at Twitter. In 2013, I worked on moving t.co, the URL shortening service created by Twitter, from physical host to Mesos service.