Joey Parsons is the Founder & CEO of effx. He’s spent his career building cloud infrastructure, running microservices and managing platform & reliability engineering teams at companies like Airbnb, Flipboard, SugarCRM, and Rackspace. This article was originally published on the effx blog.
For engineering teams, getting product into the hands of customers as quickly and reliably as possible is top priority. A move to a “you build it, you run it” and DevOps model has helped.
Microservices have also been the go-to avenue to get there. Teams have clearly understood the benefits of microservices (speed, scale, flexibility, and resilience), but…
The complexity and reliability of microservices are some of the biggest challenges that engineering teams continue to face. Having experienced the chaos first-hand while running site reliability at Airbnb, we started effx to help you tackle it with ease and prepare for the future.
We’ve spent countless hours talking to software engineers, site reliability teams, IT professionals, and engineering leaders. One common theme rang true: modern software infrastructure is comprised of distributed, complex components. A growing number of leading companies have made a shift to microservices, orchestrated by Kubernetes, AWS Lambda, Amazon ECS, and more.
These heterogeneous environments provide engineering…
One thing I’ve been asked frequently over the past few months is why do we at effx feel it’s important to introduce a new service catalogue? From an ITIL perspective, there’s plenty of tools that already exist. What makes something geared around microservices different than the solutions of the past?
The advent of microservices, more recently driven by technology like containers and their orchestration systems, has made it more complex to understand what exactly is what in your architecture.
We’ve found that the cognitive overhead of simply remembering a microservice’s intended purpose becomes difficult once you hit the 20 services…
When migrating to a service oriented architecture from the grasp of a monolith, there are plenty of technical considerations to make. Teams will spend countless hours debating the merits (or not) of monorepos, the benefits of Kubernetes over ECS (or vice versa), what open source or third party monitoring and introspection tools they’ll use to diagnose issues and countless other common workflows that are important for the microservices platform they’re building.
However, one key effort that usually gets overlooked is defining what service ownership means within your engineering organization in this new, microservices world.
So what really is service ownership?
We’ve been parents for 10 days now and while it’s easily been the most rewarding experience of my life, it’s simultaneously been the most challenging.
We sadly haven’t been able to venture outside much due to both the smoky air conditions (little one was born on the worst air day in SF history) from the recent fires and the rain that followed. So, we’ve been cooped up indoors with just us and the baby.
We received so many tips from friends and family over the past few months so I won’t reiterate much of what you can find elsewhere. We’re…