<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[effx - Medium]]></title>
        <description><![CDATA[Get to know your microservices - Medium]]></description>
        <link>https://medium.com/effx?source=rss----ba28d3eac33a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>effx - Medium</title>
            <link>https://medium.com/effx?source=rss----ba28d3eac33a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:09:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/effx" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is a microservice catalog?]]></title>
            <link>https://medium.com/effx/what-is-a-microservice-catalog-27eebfdfa692?source=rss----ba28d3eac33a---4</link>
            <guid isPermaLink="false">https://medium.com/p/27eebfdfa692</guid>
            <category><![CDATA[site-reliability]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[infrastructure-management]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[joey parsons]]></dc:creator>
            <pubDate>Wed, 27 Jan 2021 21:48:50 GMT</pubDate>
            <atom:updated>2021-01-27T21:48:08.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2TLGoicy25CXQeNjVYWcaw.png" /></figure><p><em>Joey Parsons is the Founder &amp; CEO of effx. He’s spent his career building cloud infrastructure, running microservices and managing platform &amp; reliability engineering teams at companies like Airbnb, Flipboard, SugarCRM, and Rackspace. This article was originally published on the </em><a href="https://www.effx.com/blog/what-is-a-microservice-catalog"><em>effx blog</em></a><em>.</em></p><p>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 <a href="https://www.effx.com/blog/the-evolution-into-devops-and-why-it-works-today">DevOps model</a> has helped.</p><p>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 also for many, there’s definitely been some hesitation given the overhead and specialized engineering talent needed to migrate to, operate, and scale this environment.</p><p>As more organizations move to building their products and platforms using microservices, engineering teams need an overall view of everything running in their entire, complex infrastructure. This is <a href="https://www.effx.com/blog/why-nows-the-time-for-a-new-microservice-catalog">why now’s the time for a microservice catalog.</a></p><p><strong>So what’s a microservice catalog?</strong></p><p>A microservice catalog is a flexible, portable, accurate, and intelligent view of all your microservices. It provides each engineer critical information like an aggregate of all microservices and their metadata, <a href="https://www.effx.com/blog/service-ownership-in-a-microservices-world">service ownership</a>, dependencies, how to operate, and take action on each service when an incident happens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2pN-ux4g6rKmBvya" /><figcaption><em>A detailed service view in a microservice catalog</em></figcaption></figure><p>At effx, the microservice catalog is the basic building block of how we help our customers along their journey with microservices. Below are just some of the things it helps your engineering teams with based on a combination of what we’ve experienced as practitioners and working with hundreds of the top engineering organizations around the world.</p><ul><li>The ability to search for and discover all of your microservices no matter what infrastructure or platform they’re running on</li><li>Ensuring you build microservices with excellence in mind and emphasizing quality is consistent across your company</li><li>Keeping your microservices up-to-date through the constant change of migrations</li><li>Having confidence and necessary context during complex microservice incidents</li></ul><p>However, not all microservice catalogs are built the same. And since this isn’t our first time building a microservice catalog, we’ve found that there’s key tenets to how we’ve built ours that will help you get the most out of it.</p><h3>Flexibility</h3><p>There are common challenges that most engineering teams using microservices face on a regular basis. However, if you ask an engineer at two separate organizations for the most important metadata to track for a service, that commonality ends. The language used to describe what are seemingly common attributes may be completely different!</p><p>For example, what one organization may describe as a “tier” of service, another may call it a “priority”. A “group” versus “pod”. Some may care deeply about tags for compliance while others may not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t2zoIMDqgZ2xts1-" /><figcaption><em>the effx microservice catalog allows you to define your taxonomy in code</em></figcaption></figure><p>One team may prioritize dashboards that combine both time-series data and logs into one, while others may have a separate dashboard for each pillar of observability. Runbooks could be a separate entity or a team may have a culture of having that information directly in its alert descriptions.</p><p>Every company is different — and at times, those differences exist on a team level!</p><p>A flexible taxonomy for how metadata is described and labeled allows your team to build a microservice catalog that makes sense for your cultural engineering norms, versus fitting a strongly-opinionated structure.</p><h3>Portability</h3><p>Imagine if you could only use data from another common catalog-like service, Wikipedia … on Wikipedia.</p><p>When developers build systems to send microservice metadata or events into a platform, they expect to be able to also retrieve it to use in their own applications. An API-first microservice catalog is a must.</p><p>Once the metadata for a service is aggregated into a single location, the applicability of that data in other platforms is nearly limitless. Source of truth information like service ownership can help drive priorities or roles and responsibilities in other platforms that require it.</p><p>Having a well-documented, easy-to-use API that has strong library support and follows common access patterns like REST helps ensure that your platform is both extensible and portable.</p><p><a href="https://effxhq.github.io/effx-api-v2/"><strong>Check out our effx API documentation</strong></a></p><h3>Accuracy</h3><p>In the sales world, folks describe CRMs as only being as useful as the data inside of it. A microservice catalog is no different.</p><p>Beyond being appropriately filled out, engineers need to feel confident that the data is up-to-date. A single pane of glass with incorrect information, whether it be broken links or out-of-date data can actually be more harmful than the absence of data.</p><p>How does one go about providing an accurate catalog? Most importantly, you want to make it simple and easy to keep up-to-date by having that process live where your engineers are every day: in code.</p><p><strong>Learn more about our </strong><a href="https://effx.com/help/#using-github-actions"><strong>Github Actions</strong></a><strong>, </strong><a href="https://effx.com/help/#using-gitlab-ci-cd-jobs"><strong>GitLab CI/CD Jobs</strong></a><strong>, and </strong><a href="https://github.com/effxhq/vcs-connect"><strong>vcs-connect</strong></a><strong>, our open source version control indexer.</strong></p><h3>Intelligence</h3><p>Last but not least, a microservice catalog needs to move beyond static, searchable information and help engineers derive unique insights to help them in their day-to-day.</p><p>Combining microservice event data with the overall connectedness of microservices to one another, you can provide intelligence where even your best engineers have a blind spot.</p><p>Dependencies, like which services are talking to one another, can change after a simple deploy. Having this information when the system goes awry and related to events within your infrastructure can up-level your frontline engineer’s incident response ability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x2HfLxn-Zi0x2x02" /><figcaption><em>A microservice catalog activity feed with critical dependency events inline</em></figcaption></figure><p>The key benefits of microservices like speed, scale, autonomy and resilience are only unlocked by organizations that invest in their engineers’ abilities to better navigate, operate, and evolve its microservices day-to-day. The effx platform, and its unique approach to a microservice catalog, is here to help your team turn its pain into a competitive advantage.</p><p>Want to learn more? <a href="https://app.effx.com/sign_up"><strong>Sign up for a free trial</strong></a> and start building your microservice catalog today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27eebfdfa692" width="1" height="1" alt=""><hr><p><a href="https://medium.com/effx/what-is-a-microservice-catalog-27eebfdfa692">What is a microservice catalog?</a> was originally published in <a href="https://medium.com/effx">effx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The simplest way to navigate and operate your microservices]]></title>
            <link>https://medium.com/effx/the-simplest-way-to-navigate-and-operate-your-microservices-52f1e4113a23?source=rss----ba28d3eac33a---4</link>
            <guid isPermaLink="false">https://medium.com/p/52f1e4113a23</guid>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[joey parsons]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 16:00:49 GMT</pubDate>
            <atom:updated>2020-07-20T16:00:10.004Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>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.</em></strong></p><p>We’ve spent countless hours talking to software engineers, site reliability teams, IT professionals, and engineering leaders. One common theme rang true: <strong>modern software infrastructure is comprised of distributed, complex components. </strong>A growing number of leading companies have made a shift to microservices, orchestrated by Kubernetes, AWS Lambda, Amazon ECS, and more.</p><p>These heterogeneous environments provide engineering teams the advantage of using the best platforms for each piece of functionality, building leverage for their digital businesses. However, the additional complexity comes at a cost. The cognitive load on each engineer can be extremely overwhelming when they need to answer questions about each service, its dependencies, or the system as a whole. It’s a confusing, constantly moving target and can be downright frustrating, especially during downtime.</p><p>Speaking of downtime, the reliability challenges of yesteryear have led to a cultural shift where all engineers — not just highly trained site reliability engineers — now fully own and operate services. The ease and speed of development with microservices can be at odds with the breadth of knowledge required to expertly navigate and operate them. Simply orienting around a bug, security flaw, or incident has become challenging. The lack of context with complex incidents leads to lengthy downtime that in turn results in lost business value and trust with your customers.</p><p>Existing monitoring tools, CMDBs, wikis, and of course, spreadsheets weren’t designed to handle all these dynamic moving pieces and unplanned downtime.</p><p><strong>effx is here to change that.</strong></p><p><strong>Easily navigate your way through each microservice</strong></p><p>Whether you’re just getting started or have thousands of microservices, effx helps engineering teams navigate their journey, regardless of orchestration system, public cloud, or on-premise environment.</p><ul><li>Build your catalogue with deep integrations into Kubernetes, AWS Lambda, Amazon ECS, GitHub and GitLab</li><li>Understand all of your services at a glance</li><li>Track service ownership and keep it up-to-date across organizational changes and the day-to-day development by your team.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WGEfEIibxn43KUdf" /></figure><p><strong>Gain rich context and faster response times during complex incidents</strong></p><p>Incidents across a fleet of microservices are rarely simple. effx provides context to help you quickly orient around the potential causes of an incident.</p><ul><li>Understand how your services and their dependencies change from deploys, feature flags, experiments, capacity changes and more with effx’s real-time activity feeds</li><li>Operate your microservices with confidence by providing the best links to your observability tooling, runbooks, documentation and version control</li><li>Get a birds eye view of how your services and their dependencies interact with one another to quickly scan for recent events and active incidents</li></ul><p><strong>Keep services healthy and production ready</strong></p><p>You’ve invested in your ability to know when production breaks. We help you proactively prepare for those moments by scoring services on key attributes that ensure services are continually monitored and documented.</p><ul><li>Know the areas in your organization where efforts should focus to improve resiliency</li><li>Report on which services are running vulnerable language versions or are frequently experiencing downtime</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vUOVUdLQzpkqNGQn" /></figure><p>We hope you’ll join us on your journey to service excellence and get back to building world-class experiences for your customers. Leave the microservices to us.</p><p><a href="https://app.effx.com/sign_up"><strong>Sign up for a 14-day trial today!</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f1e4113a23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/effx/the-simplest-way-to-navigate-and-operate-your-microservices-52f1e4113a23">The simplest way to navigate and operate your microservices</a> was originally published in <a href="https://medium.com/effx">effx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why now’s the time for a new (micro)service catalogue]]></title>
            <link>https://medium.com/effx/why-nows-the-time-for-a-new-service-catalogue-dde39acdadc8?source=rss----ba28d3eac33a---4</link>
            <guid isPermaLink="false">https://medium.com/p/dde39acdadc8</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <dc:creator><![CDATA[joey parsons]]></dc:creator>
            <pubDate>Thu, 16 Jan 2020 16:47:15 GMT</pubDate>
            <atom:updated>2020-01-16T16:48:47.700Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GoM07r4Xx0Z_FRz65Ajt1A.png" /></figure><p>One thing I’ve been asked frequently over the past few months is why do we at <a href="https://effx.com/">effx</a> 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?</p><p>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.</p><p><strong><em>We’ve found that the cognitive overhead of simply remembering a microservice’s intended purpose becomes difficult once you hit the 20 services mark.</em></strong></p><p>Why is it so difficult? Beyond <a href="https://medium.com/effx/service-ownership-in-a-microservices-world-ee3c7904a720?source=friends_link&amp;sk=e4daa14441410a17caf73744564907f1">challenges with service ownership</a>, let’s discuss a few of the reasons:</p><p><strong>Naming things is hard</strong></p><p>I won’t repeat the quip about the most difficult things in Computer Science, but when it comes to naming services, it’s an incredibly difficult thing to do. No naming scheme scales to hundreds of microservices, much less thousands. Let’s take a microservice whose purpose is pricing as an example:</p><ul><li>You could name it “pricing” and call it a day, but might end up being too ambiguous for all of the different roles a “pricing” service might have. Also, imagine trying to search across a company wiki for “pricing” to get details about it and ending up finding literally every mention of the word across things like pricing of your corporate insurance, marketing documents on pricing &amp; packing or an offhand comment on a design doc unrelated to the “pricing” service.</li><li>Or, let’s say you’ve been naming microservices at your company after Game of Thrones lore and you call it the “ironbank” or “braavos” microservice. Sure, there may be some relation between pricing and those terms, but if everyone hasn’t carefully watched or read The Song of Fire &amp; Ice, they won’t get the reference — and it may not even totally be accurate.</li></ul><p>We’ve seen most companies choose the latter option. This makes it critical to be able to search and find based on the name (if you already know braavos exists) or its purpose (“the pricing service”) in the service catalogue.</p><p><strong>Using the best language for the job</strong></p><p>One clear benefit of having a monolith is that it’s a simple entity: written in one language, one deployment system, and one giant codebase for your engineers to fully grok. However, when you switch to a microservices architecture, most engineering organizations allow the flexibility of choosing the best language possible for the intent of that service.</p><p>When you end up using a variety of languages — or even versions of those languages — things can become difficult to track. Was that pricing service written in Go? Or is it one of the few services we decided to build on the JVM? Wait, did we upgrade it to Java 8 and which JDK? Hmm. Was this a data analysis service that we wrote in Python? Did we actually upgrade all of the similar services when the recent vulnerability hit?</p><p>All of these questions about what something is can be answered with a new, modern service catalogue that keeps track of the technologies, languages, and libraries — and the versions used! — across your fleet.</p><p><strong>The proliferation of dashboards</strong></p><p>I’m sure you’ve seen it by now. For each “pillar of observability” you and your team have chosen the best-of-breed tool. You’ve gone through the effort of building custom dashboards in your logging tool or maybe you’re using the canned dashboards for viewing time series data. Your AWS cost tool is on another dashboard and maybe there’s one for operational understanding and another for your finance team.</p><p>When things go wrong with your microservice, how do you make sure everyone on your team is starting from the same place before deep diving? Do you share bookmarks? How do you keep them up-to-date and in-sync across the team?</p><p>Ensuring that your service catalogue has the most up-to-date links to the different tools you use every day so that everyone on your team — and everyone across your engineer organization — can jump to the right tool at the right time when they need it most.</p><p><strong>Different tiers of importance for microservices</strong></p><p>Not every microservice is the same — not just from the aspect of being business critical, public facing, or some hierarchical, numerical tier. Each microservice has properties that aren’t necessarily properties that other microservices would inherently share.</p><p>Sure, service catalogues may track a singular group that a service belongs to or a tier of service. A modern service catalogue would allow freeform key-value pairs to track things that are important to you with common patterns that we’ve seen. You should be able to track that a service belongs to a group (or many!), has a particular tier that matches how you define tiers internally, and maybe other items like:</p><ul><li>this service is in scope for GDPR, or HIPAA</li><li>how is the service deployed or orchestrated e.g. deployment via kubernetes or ECS</li><li>is it tagged for a large internal migration from one platform to another and where is it along its journey</li></ul><p>… and the possibilities are endless.</p><p>All of the above are organizational challenges that a modern engineering team faces when fully operating a microservices architecture. At effx, we’ve built our new service catalogue to address these specific concerns and especially, how to ensure that they’re always up-to-date.</p><p>With integrations into Kubernetes, serverless platforms, and by hooking into your existing tagging schemes, we can import your catalogue and begin helping you shape it to always be up-to-date, accurate, and dynamic enough to ensure that it’s the most helpful tool to know what something is when you need it most.</p><p>Sign up for a demo at <a href="https://effx.com/">https://effx.com</a> to hear about how this can solve your toughest organizational and microservices challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dde39acdadc8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/effx/why-nows-the-time-for-a-new-service-catalogue-dde39acdadc8">Why now’s the time for a new (micro)service catalogue</a> was originally published in <a href="https://medium.com/effx">effx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KubeCon First Timer? Me too!]]></title>
            <link>https://medium.com/effx/kubecon-first-timer-me-too-dcf0b31cd60?source=rss----ba28d3eac33a---4</link>
            <guid isPermaLink="false">https://medium.com/p/dcf0b31cd60</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[kubecon]]></category>
            <dc:creator><![CDATA[Morgan McIntyre]]></dc:creator>
            <pubDate>Thu, 14 Nov 2019 22:10:44 GMT</pubDate>
            <atom:updated>2019-11-14T22:05:08.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SNb32lumutOdqv3F6hsr3g.png" /></figure><p>For those who don’t know much about effx, we are a small startup composed of tech enthusiasts who just launched in October (which is probably why you haven’t heard much about us yet. Don’t worry, I’m here to shed some light!) and we are heading to KubeCon 2019 in San Diego!</p><p>You might be asking yourself, what exactly is “effx” and why are we going to KubeCon?</p><p>We are building a platform to help engineering teams better manage, understand and easily operate their service-oriented architecture. We do this by helping engineering teams keep track of what’s across their full fleet of microservices, discover what has changed within each microservice, and ensure that ownership and microservice metadata is up-to-date and regularly verified.</p><p>As the growth and usage of container orchestration tools becomes more and more relevant to the tech industry, our goal is to bring an elegant experience to those engineering workflows. The founder of effx, Joey Parsons who is a former infrastructure leader at Airbnb saw these problems first-hand and knew this was a pain point that needed to be solved. Read more in his recent article on <a href="https://medium.com/effx/service-ownership-in-a-microservices-world-ee3c7904a720">Service Ownership in a Microservices World.</a></p><p>With Kubernetes going into its 5th official year, moving from infancy to being adopted by most companies with a modern infrastructure, there is no better time to help make the use of Kubernetes even more seamless.</p><p>And what better way to introduce effx to the tech community than showcase our product at the biggest Kubernetes event of the year! An event where companies who use microservices from all over the world, varying from large cloud providers like Amazon Web Services to Google Cloud all the way to small startups our size. As a seven person startup with a modern tech stack and a small Kubernetes footprint — we would be crazy if we missed this event.</p><p>For those of you who aren’t familiar with KubeCon, it’s the largest gathering for Kubernetes topics hosted by the Linux Foundation. According to the Linux Foundation, “2018 marked a tipping point for open source, which <a href="https://www2.thelinuxfoundation.org/webmail/6342/941750253/a62ceb6340695d8e087ac6f894239537">drove more than $65 billion in mergers, acquisitions, and IPOs</a> (which Kubernetes played a large part in).” KubeCon has grown in attendance since 2015, starting with 500 people to over 8,000 people in 2018 and has continued to grow in 2019.</p><p>—</p><p>So why is someone who comes from a business background — who doesn’t have a CS degree or come from a software engineering background — excited for KubeCon?</p><p>My first job after college was a recruiting position where I specialized in recruiting software engineers — more specifically DevOps and Security. This was a major learning curve for me because I came from a business background with no experience in the tech industry in general. Talking and connecting with DevOps engineers on a daily basis taught me a lot about the industry, I have gained so much knowledge in areas that I never knew much about (i.e. CI/CD, containers, microservices, kubernetes, serverless architecture, etc.)</p><p>I used these fundamentals as a base to help me plunge into the land of startups where I got the opportunity to join a company whose product is helping alleviate a lot of the pains that I would hear engineers talk about on a daily basis.</p><p><em>Back to the “why” — </em>KubeCon is a great opportunity to talk with people about our product and learn even more about this ever-growing and ever-changing industry. If there’s anything I’ve learned thus far in my life and career, it’s that knowledge is key. The more you know, the better off you are both in your personal and professional life and I’m personally excited to use this event as building blocks for my future, and the future of effx.</p><p>Are you going to KubeCon? Come meet us there! You can find us in the Startup Sponsor section where we will be giving demos and would love to answer any lingering questions you might have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf0b31cd60" width="1" height="1" alt=""><hr><p><a href="https://medium.com/effx/kubecon-first-timer-me-too-dcf0b31cd60">KubeCon First Timer? Me too!</a> was originally published in <a href="https://medium.com/effx">effx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Ownership in a Microservices World]]></title>
            <link>https://medium.com/effx/service-ownership-in-a-microservices-world-ee3c7904a720?source=rss----ba28d3eac33a---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee3c7904a720</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[software-engineer]]></category>
            <dc:creator><![CDATA[joey parsons]]></dc:creator>
            <pubDate>Thu, 07 Nov 2019 21:31:34 GMT</pubDate>
            <atom:updated>2019-11-07T21:24:51.394Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Llh8e_FXTBXPNFMGUX7-ag.png" /></figure><p>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.</p><p><strong><em>However, one key effort that usually gets overlooked is defining what service ownership means within your engineering organization in this new, microservices world.</em></strong></p><p>So what really is service ownership?</p><p>There’s quite a few amazing articles written about the “code it, ship it, own it” portion of service ownership, especially as it pertains to on-call and incident management. See Julie Gunderson’s recent write up on <a href="https://opensource.com/article/19/9/code-it-ship-it-own-it-fso">Code it, ship it, own it with full-service ownership</a> and the venerable Liz Fong-Jones’s article on <a href="https://www.infoq.com/articles/production-excellence-sustainable-operations-complex-systems/">Sustainable Operations in Complex Systems with Production Excellence</a>.</p><p>Beyond on-call, there’s so much more that goes into the day-to-day of what a service owner is called upon for, including:</p><ul><li>Being the point of contact for the security team when any priority security issue is raised</li><li>Staffing a Slack channel to help answer questions about how to integrate with your service or being helpful</li><li>Keeping its documentation and runbooks up-to-date as best you can</li><li>Ensuring that observability dashboards are easy-to-find, easy-to-peruse, and have suitable tools to be able to dig deeper and analyze</li><li>Planning and adapting for capacity and ensuring performance is efficient as possible</li><li>Making future on-call rotations better by learning from the current and past</li><li>Fixing and triaging bugs, diving into performance issues, speeding up builds, and of course, all the toil and yak-shaving that we spend a large share of our time on</li></ul><p><strong><em>Now imagine an engineering organization where service ownership isn’t well-defined or implemented and how all of the above breaks down.</em></strong></p><p>— —</p><p>Earlier this year, we researched the efforts of a handful of engineering teams ranging from early-stage startups who went all-in on microservices from the get go, to large enterprise teams who had recently slogged through multi-year journeys (many still in progress) from monoliths to a microservices approach.</p><p>There were a few common themes, but most importantly, most teams struggled with the concept of service ownership. Cultural issues were a noted cause. The lack of tooling another. A gap in understanding from what the infrastructure team intended to hand off in terms of their responsibilities to the service owners.</p><p>Everyone struggled with all of these same things.</p><p><strong><em>Unowned services — and discovering them — causes unending pain.</em></strong></p><p>Imagine a world where a vulnerability hits a language or platform you use in the lion’s share of your microservices. And then imagine someone in your organization — a project manager or a security engineer — building a spreadsheet of all the affected services, noting the owners of the service for follow up, and managing the landscape of hundreds (or thousands) points of coordination to ensure that everything is completed in a timely fashion. That person finds new owners for the orphaned services and all is well. Phew.</p><p>And then a new vulnerability hits that same language or platform 90 days later. Again, the fix could be something as simple as build, validate, deploy — that could even be fully automated — but requires someone familiar with the service to fully ensure compatibility or if something goes terribly wrong. Since the last issue, there’s been a few changes in the engineering organization and maybe the first few teams you contact about getting the process started no longer exist. That project manager has to essentially start from zero on a new spreadsheet and re-validate that services are still owned by the same teams or find the proper mapping.</p><p>From our research, this is happening at nearly every company we talked to.</p><p><strong><em>HR systems manage to get updated when re-orgs happen or people change teams, but somehow, service ownership is left outdated.</em></strong></p><p>One of the issues that came up frequently in our research was the opinion that service ownership issues were related to cultural issues in engineering. An apathy for having the tough conversations about who should own what when there’s a dispute after one team’s charter has changed and left their old projects behind.</p><p>And yet, teams will take on the risk of leaving an unowned service in production and have that tough conversation when downtime or tragedy befalls that service.</p><p>If your organization can keep Workday or Namely up-to-date with who reports to who, shouldn’t an engineering team be able to make — in turn — the updates to a system that keeps track of who owns what?</p><p>— —</p><p>One of the reasons I started building <a href="https://effx.com/">effx</a> was because I saw some of these challenges and issues while running reliability engineering at Airbnb. We built an internal tool to track ownership in code (yaml, of course) that we did our best to keep up-to-date. It still required a project manager frequently running around the halls to keep the information current.</p><p>When we were able to corroborate our findings with peer companies that had recently began, were in the middle of, or had finished their journey to microservices, we set out to build a tool that could overcome the cultural challenges our friends had spoken of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BglkZqACsAFGrshJeD9psA.png" /><figcaption>effx ownership flow</figcaption></figure><p>By invoking some timely flows and an elegant interface to continually validate ownership, keep it up-to-date, and resolve conflicts, we hope that we can help you and your team free up that project manager’s time, eliminate unowned services and prevent them from recurring.</p><p><em>Want to learn more about service ownership from an effx perspective? Sign up to get a demo of our platform at </em><a href="https://effx.com/"><em>https://effx.com</em></a><em> or reach out and chat more at @joeyparsons on twitter or email at joey [at] effx.com.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee3c7904a720" width="1" height="1" alt=""><hr><p><a href="https://medium.com/effx/service-ownership-in-a-microservices-world-ee3c7904a720">Service Ownership in a Microservices World</a> was originally published in <a href="https://medium.com/effx">effx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>