Rootconf Pune edition

On security, network engineering and distributed systems


Journey of Hotstar Infra from EC2 to containers

Submitted by Prakhar Joshi (@prakharj) on Friday, 26 July 2019

Section: Full talk (40 mins) Category: DevOps

View proposal in schedule


This talk will focus on Hotstar’s journey from EC2 to Kubernetes. The main reasons for migrating to kuberntes was the challenges and limitations we faced while scaling infrastructure of Hotstar at peaks. This talk will also cover challenges faced during migrations and performance tuning of applications on containers.


  1. About Hotstar
  2. Hotstar at IPL 2018
  3. Ec2 challenges at Scale
  4. Migration to kubernetes
  5. Challanges in kubernetes migration
  6. Performance tuning for IPL‘19 and WC
  7. Hotstar at IPL‘19/WC

Speaker bio

Prakhar is Infrastructure Engineer at Hotstar, India’s leading OTT provider that holds a global concurrency record for live streaming to 25Mn+ viewers. At Hotstar, he loves automating deployments using terraform and scale infrastrure of hotstar on kubernetes. He is also passionate about Infra security.


  • Zainab Bawa (@zainabbawa) Reviewer 25 days ago

    Thanks for an interesting proposal, Prakhar. We will confirm your talk as a crisp talk for Rootconf Pune. We will update you about pre-event rehearsal and speaking policies of Rootconf Pune in this week.

  • Zainab Bawa (@zainabbawa) Reviewer 2 hours ago

    Thanks for the rehearsal yesterday, Prakhar. Here are the feedback points and changes to be made to the slide and flow of the presentation:

    1. Context about Hotstar should be shortened and limited to the journey you are discussing.
    2. Why was EC2 used in the tech stack to start with? Why was the tech stack what it was, when you started? (This is because you explained the tech stack before the migration. So in addition to explain what, you should also state why this stack/architecture was chosen in the beginning.) You have explained what was the limitation with EC2, but why EC2 was used in the first place hasn’t been explained.
    3. Show a table of the before-and-after Kubernetes situation. This will help the audience get the context.
    4. The migration section can be made crisper. Some visuals or diagrams will help, here.
    5. Game day readiness slide could also have a visual.
    6. Maybe an architecture diagram, which serves as an anchor slide, will help. You can keep referring to the diagram to show before-and-after situation. You can also consider animating this diagram.
    7. Presentation needs a concluding slide with your learnings.
    8. Move your contact information details towards the end, since participants will be more cued to noting your contact details at the end of the session, rather than at the beginning.

    Submit your revised slides by 31 August, latest, so that we can schedule a second rehearsal in the first week of September.

Login with Twitter or Google to leave a comment