<?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[Stories by Ayan Sen on Medium]]></title>
        <description><![CDATA[Stories by Ayan Sen on Medium]]></description>
        <link>https://medium.com/@ayansen89?source=rss-c557c42ba610------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pRKYl9EoFuGZajXkL7Civw.jpeg</url>
            <title>Stories by Ayan Sen on Medium</title>
            <link>https://medium.com/@ayansen89?source=rss-c557c42ba610------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:09:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayansen89/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Configuration Management at Expedia Group]]></title>
            <link>https://medium.com/expedia-group-tech/configuration-management-at-expedia-group-a23a7563a348?source=rss-c557c42ba610------2</link>
            <guid isPermaLink="false">https://medium.com/p/a23a7563a348</guid>
            <category><![CDATA[travel-platform]]></category>
            <category><![CDATA[multitenancy]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[platform-as-a-service]]></category>
            <category><![CDATA[configuration-management]]></category>
            <dc:creator><![CDATA[Ayan Sen]]></dc:creator>
            <pubDate>Tue, 22 Aug 2023 11:02:23 GMT</pubDate>
            <atom:updated>2023-08-22T11:02:23.225Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/expedia-group-tech/engineering/home">EXPEDIA GROUP TECHNOLOGY — ENGINEERING</a></h4><h4>How we model partner-specific behavior as configurations</h4><figure><img alt="Two people stand-up paddleboard on a lake with mountains in the background." src="https://cdn-images-1.medium.com/max/1024/0*YFIlxADGx-hQq3It" /><figcaption>Photo by Matt Zhou on Unsplash</figcaption></figure><h3>Overview</h3><p>In recent years, <a href="https://www.expediagroup.com/">Expedia Group</a>™️ has shifted its focus to becoming a platform company, recognizing the need to better serve its partners. We are transforming the technology stack into a large multi-tenant platform, where each partner can have a white-label version of Expedia Group’s travel offerings or access our API Products. The platform is highly configurable to cater to each partner’s requirements. This required significant changes to the platform, but at its core, we needed a configuration system that could be leveraged to model partner-specific behavior as configurations.</p><h3>Challenges</h3><p>The existing stack had configurations spread across different infrastructures, stored in disparate systems adopting different data models, and sometimes hard-coded. This meant adding a partner to the platform required changes in many places, taking us multiple months to onboard a partner.</p><figure><img alt="Current state of configurations spread across disparate systems" src="https://cdn-images-1.medium.com/max/1024/1*cozp0Wv_V3oHAAltXF3q_A.png" /></figure><h3>Solution</h3><p>We built the Control Plane to provision and manage partners efficiently and optimally. An integral part of the Control Plane is a Platform Configuration System. The Control Plane leverages the Platform Configuration System to manage configurations for the partners. Platform Configuration is the service that manages, stores, and distributes configuration data used to control partner behavior across the platform.</p><figure><img alt="Diagram showing partners configuring there capabilities and the travel platform consuming them while serving traffic for the partner" src="https://cdn-images-1.medium.com/max/720/1*4-NDf5ZazyrRrmSDVsqnVg.png" /></figure><h4>Configuration semantics</h4><p>Services are configured to behave differently for different partners. For example, a flight service might have different configurations for allowed currency, airlines or fare options for a given partner. A checkout service might have different configurations for different payment methods, such as credit card, PayPal, or Apple Pay.</p><p>These configurations are not arbitrary, but have to follow some rules or constraints that are defined by the service owners. For example, a flight service might require that the currency configuration is one of the valid ISO 4217 codes, such as USD, EUR, or JPY or the payment method configuration is one of the supported options, such as Visa, Mastercard, or American Express.</p><p>These rules or constraints are expressed as a <a href="http://json-schema.org/">JSON Schema</a>, which is a standard way of describing the structure and validation of JSON data. JSON Schema allows you to specify what properties an object should have, what type and format each property should be, what values are allowed or required for each property, and how to handle errors or missing data. JSON Schema also enables clear and concise documentation of the data format and validation logic.</p><p>The service owners use the platform-configuration APIs to publish their JSON Schema to a central system that manages all the configurations for different services and domains. The platform-configuration APIs are a set of interfaces that allow you to create, retrieve, update and delete (CRUD) configurations in a consistent and secure way. The system provides syntactic validation using a JSON Schema validator against the declared types. This means that the system checks if the configuration data conforms to the JSON Schema and rejects any invalid or malformed data.</p><p>The system also supports registering an Extension (Callback API) if the service requires business configuration data validation. This means that the system can invoke a custom function or service that performs additional logic or checks on the configuration data before accepting it. For example, a flight service might register an Extension that verifies if the currency configuration matches the region configuration. A car service might register an Extension that calculates the total price based on the size and color configurations. A checkout service might register an Extension that validates the payment method configuration against a third-party provider.</p><p>The type contains a key-spec attribute that dictates how the configuration should be keyed, for example, key-spec = [partner, country]<strong> </strong>can contain configuration instances for keys my_travel_company/US<strong>, </strong>my_travel_company/UK and so on.</p><p><strong>Sample type</strong></p><pre>{ <br>  &quot;key&quot;: &quot;grocery/v1/vegetable&quot;, <br>  &quot;spec&quot;: { <br>    &quot;$schema&quot;: &quot;http://json-schema.org/draft-04/schema#&quot;, <br>    &quot;title&quot;: &quot;vegetable&quot;, <br>    &quot;description&quot;: &quot;a vegetable&quot;, <br>    &quot;key_spec&quot;: [ <br>      &quot;name&quot; <br>    ], <br>    &quot;type&quot;: &quot;object&quot;, <br>    &quot;properties&quot;: { <br>      &quot;name&quot;: { <br>        &quot;description&quot;: &quot;a description of the vegetable&quot;, <br>        &quot;type&quot;: &quot;string&quot; <br>      }, <br>      &quot;color&quot;: { <br>        &quot;description&quot;: &quot;the color of the vegetable&quot;, <br>        &quot;type&quot;: &quot;string&quot; <br>      } <br>    }, <br>    &quot;required&quot;: [ <br>      &quot;name&quot;, <br>      &quot;color&quot; <br>    ] <br>  }, <br>  &quot;labels&quot;: { <br>    &quot;managed_by&quot;: &quot;grocer&quot; <br>  }, <br>  &quot;status&quot;: &quot;LIVE&quot; <br>} </pre><p><strong>Sample instance</strong></p><pre>{ <br>  &quot;key&quot;: &quot;tomato&quot;, <br>  &quot;spec&quot;: { <br>    &quot;description&quot;: &quot;a regular tomato&quot;, <br>    &quot;color&quot;: &quot;red&quot; <br>  }, <br>  &quot;status&quot;: &quot;LIVE&quot; <br>} </pre><h4>Relations</h4><p>The configuration system incorporates a reference feature, which enables configurations to point to other configurations (either fully or partially). This feature acts as a foundation for creating intricate configuration hierarchies and establishing defaults while onboarding a partner.</p><p><strong>Sample relation</strong></p><pre>{ <br>  &quot;key&quot;: &quot;tomehto&quot;, <br>  &quot;spec&quot;: { <br>    &quot;$uri&quot;: &quot;storage:grocery/v1/vegetable/tomato&quot; <br>  }, <br>  &quot;status&quot;: &quot;LIVE&quot; <br>} </pre><p><strong>Sample relation — resolved</strong></p><pre>{ <br>  &quot;key&quot;: &quot;tomehto&quot;, <br>  &quot;spec&quot;: { <br>    &quot;description&quot;: &quot;a regular tomato&quot;, <br>    &quot;color&quot;: &quot;red&quot; <br>  }, <br>  &quot;status&quot;: &quot;LIVE&quot; <br>} </pre><h4>Configuration distribution</h4><p>Platform Configuration System captures and distributes the configurations to all the Expedia Group services by streaming updates out to Configuration Syncs which run locally in the consumer’s infrastructure. This allows every service to consume configuration data locally at low latencies without introducing a single point of failure from the Control Plane. If the Platform Configuration System is unavailable, the services run with the latest configuration state they have locally. The Configuration System resolves references before streaming updates to Configuration Sync, resulting in quick and straightforward reads.</p><figure><img alt="Diagram showing configuration distribution where configurations are distributed to different syncs" src="https://cdn-images-1.medium.com/max/814/1*Na9MgeTBO7QoJ5lfdaRDXA.png" /></figure><h4>Configuration provider</h4><p>Although the model is theoretically unified and centrally accessible, ownership and technical considerations mean that it may not reside in a single physical system. The architecture enables federation by registering a configuration provider. Leveraging that, service owners can continue using their existing configuration mechanisms to read the configurations if they are defined as a provider with the configuration system.</p><figure><img alt="Diagram showing configuration provider where configurations are powered by existing configuration systems" src="https://cdn-images-1.medium.com/max/586/1*ppnFeoVu-AP3GgrxoRSIww.png" /></figure><h3>Alternatives</h3><p>Building a system from scratch takes time and resources. There needed to be sufficient reason to build something new, instead of leveraging an existing open source or inhouse solution.</p><h4>Leveraging an existing system</h4><p>Expedia Group has used multiple different configuration systems over the years. None of these provided the feature set we now need to solve and scale for the entire company. Most configuration systems made foundational assumptions around the configuration structure/schema or how they had to be keyed, making them difficult to extend.</p><h4>Open-source solutions</h4><p>We looked at open-source software like <a href="https://zookeeper.apache.org/">Zookeeper</a>, <a href="https://etcd.io/">etcd</a> and others. None of the systems provided strongly typed configurations. Most of our business capabilities are powered by configurations, making it crucial to have strongly typed configurations.</p><h3>Conclusion</h3><p>The configuration system replaces legacy logic from various systems, such as rule engines, hierarchical configuration systems, and source code, supporting diverse use cases. It is built as a type system over HTTP, with a focus on first principles. The system only utilizes primitives such as type, instance, key, and references, which have proven to be effective in modeling all types of configurations. We found the patterns useful to build out configurations for any multi-tenant platform, powering configurable experiences across thousands of partners in a self-service way.</p><h3>Terminology</h3><p><strong>Type:</strong> Defines the schema of the Configuration. It captures the spec as a JSON Schema, along with the key-spec defining how the configuration instances should be keyed.</p><p><strong>Instance:</strong> A JSON object containing settings that control how EG Capabilities behave for a given partner. This is also called a <strong>Configuration Instance. </strong>A configuration has a spec and a key defining the configuration attributes and how it is keyed.</p><p><strong>Configuration Sync:</strong> It is a universally available local cache for reading configs. It is decoupled from Configuration Service. It stores configurations in their flattened state (with references resolved) and exposes them through a REST API.</p><p><strong>References: </strong>References let us share configuration objects and create compound configurations using composition. They can provide sensible defaults, allowing changes in base configuration to easily propagate and help reduce duplication of configuration values.</p><p><strong>Extensions: </strong>Extensions provide a path for domain owners to apply side effects/validations to the configurations they are managing through a callback API. A domain owner can register an extension for a configuration type by specifying external URLs that Platform Configuration calls when a CRUD operation is performed on any configuration of that type.</p><blockquote><a href="https://careers.expediagroup.com/life/">https://careers.expediagroup.com/life/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a23a7563a348" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/configuration-management-at-expedia-group-a23a7563a348">Configuration Management at Expedia Group</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>