Almost couple of years before, Tinder made a decision to move the platform to Kubernetes
Kubernetes afforded us a way to push Tinder Technology into containerization and you can reduced-reach procedure due to immutable implementation. App generate, implementation, and infrastructure would-be identified as code.
We were and additionally looking to target demands out-of measure and you will balances. Whenever scaling turned important, we frequently suffered as a result of several times regarding looking forward to brand new EC2 period ahead on line. The thought of pots arranging and you can serving subscribers within seconds given that not in favor of times is actually attractive to all of us.
It wasn't effortless. Throughout the all of our migration in early 2019, we attained vital size within Kubernetes group and you will first started encountering certain demands on account of traffic volume, group proportions, and DNS. I repaired fascinating pressures in order to move 2 hundred properties and focus on an effective Kubernetes people from the level totaling step one,000 nodes, 15,000 pods, and you may forty eight,000 powering bins.
Doing , we worked our very own ways as a result of various stages of your migration effort. We been by containerizing our functions and you may deploying all of them so you can several Kubernetes hosted staging environments. Delivery Oct, i began systematically moving our very own legacy qualities in order to Kubernetes. Of the February next season, we finalized our very own migration while the Tinder Program now operates exclusively toward Kubernetes.
There are other than 31 source code repositories on microservices that run regarding Kubernetes group.