Microservices are like mini companies—they are operated by a single team independently of the rest of the organization. Teams often own the whole stack, making decisions about what programming languages and frameworks to use, what technologies to utilize, and how to operate their services.
But what happens when the team moves on to the next project? Or if the team is not large enough to provide adequate on-call support? And won’t owning and being responsible for more of the things lead to less time and energy for product development?
Standardization helps unify and simplify the operations, but it might come at a cost of not being able to deliver a new product feature sooner. It is important to know what to standardize and how. As with software distributed systems, organizations must decide on the right balance between consistency and availability of operations. George Sudarkoff explains how to distribute operations in a consistent and efficient way.
George Sudarkoff is an infrastructure engineering manager at SurveyMonkey. Before embracing the world of operations, he spent a couple of decades doing software development in a wide variety of areas from financial services, semiconductor fab automation, robot control, real-time image processing, and networking to virtualization, distributed storage, and web development. In his copious spare time, George can be found rock climbing or making furniture in his wood shop.
©2016, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org