Why Kubernetes Was The Ideal Match For Buffer's Transition to Microservices
Buffer’s fully distributed engineering team is spread across 10 timezones, which can make it challenging to enact sweeping change like moving from a monolithic codebase to microservices. Remote team members had been struggling to scale their development process as we’ve grown. A couple of years ago, their team rallied around the idea that it would ship code the minute it is better than what is in production.
With a single monolithic application and a growing engineering team, this became a bottle neck and deploying their tightly coupled app started to create new challenges and problems. They needed a new way for each part of their application to deploy independently and quickly. Kubernetes was the missing piece that has allowed them to stay true to their engineering culture, empowering their team of engineers to move fast while also having a resilient and stable application infrastructure. This talk hopes to illustrate that journey and how Kubernetes has enabled their infrastructure to reflect the organization itself; a distributed group of autonomous people aiming to work together while not getting in each other’s way.
Bio:
Dan Farrelly is an Architect at Buffer, a social media management software company. He is leading up the company's efforts to move to a service oriented architecture, replacing a monolithic PHP application with lots of Node and PHP microservices using Docker and Kubernetes. Previously, he worked as a full stack developer at Buffer and a front-end developer at Slated. He also is building Timezone.io as a side project to help distributed teams make sense of timezones.
Presentation # 2: • Kubernetes & Cloud Native NYC Meetup: Stew...
Follow on Twitter:
Dan Farrelly: twitter.com/djfarrelly
Buffer: twitter.com/buffer
Timezone.io: twitter.com/timezoneio
Apprenda: twitter.com/Apprenda
Kubernetes: twitter.com/kubernetesio
Kismatic: twitter.com/kismatic
Cloud Native Computing Foundation: twitter.com/CloudNativeFdn
コメント