<?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 Gurnam Madan on Medium]]></title>
        <description><![CDATA[Stories by Gurnam Madan on Medium]]></description>
        <link>https://medium.com/@gsmadan?source=rss-14c61b8a4ab7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fWUxU6eHkBbVVRuz.jpg</url>
            <title>Stories by Gurnam Madan on Medium</title>
            <link>https://medium.com/@gsmadan?source=rss-14c61b8a4ab7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:01:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gsmadan/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[Why Data Mesh?]]></title>
            <link>https://medium.com/wesfarmers-onedigital/why-data-mesh-e6b85bb09dfa?source=rss-14c61b8a4ab7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6b85bb09dfa</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-mesh]]></category>
            <category><![CDATA[data-architecture]]></category>
            <dc:creator><![CDATA[Gurnam Madan]]></dc:creator>
            <pubDate>Wed, 26 Oct 2022 10:14:32 GMT</pubDate>
            <atom:updated>2022-10-26T10:20:51.754Z</atom:updated>
            <content:encoded><![CDATA[<p>Every organisation is investing heavily in data and analytics to have actionable insights and unlock business value. This is becoming more challenging as</p><ul><li>the size, sources &amp; complexity of data increases</li><li>expectations to reduce cycle times between <em>data</em> &gt; <em>insight</em> &gt; <em>action</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/351/1*TQO9MSMgCYBHh6usiCFW9A.png" /><figcaption>Continuous Cycle</figcaption></figure><ul><li>need for rapid experimentation to cheaply test and learn</li></ul><p>At OneDigital we are embracing a decentralised approach to data to address these challenges. We are on the journey to build our data platform capability to democratise data, enable teams to produce insights and shift left data quality &amp; governance.</p><h3>Challenges around data</h3><p>Historically organisations have taken a centralised approach to solve data challenges by having a large data team that ingests all the data, produces all the insights &amp; reporting, does data governance and becomes SME for every domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okSNECPQ3YIMky4hfVb_6g.png" /><figcaption>Centralised Approach</figcaption></figure><p>This generally leads to</p><ul><li>disempowering teams responsible for driving key metrics, as they are at mercy of a centralised team to produce insights</li><li>business rules are authored outside the domain leading to anemic domains</li><li>lack of accountability and responsibility for product teams, as value and understanding of data is lost</li><li>organisation behaviour to assign any problem statement which requires data to the central data team, without understanding which domain or product it aligns with.</li><li>Data quality issues e.g. missing data, mismatched definitions, format issues, inconsistent data</li><li>High knowledge burden and the constant pressure of delivery on the central data team</li><li>Heavy manual data governance with policies and processes</li></ul><p>In summary, cycle times to take actions are very slow resulting in lost opportunities.</p><h3>Have we seen this before?</h3><p>We can draw clear parallels when you think about how DevOps has evolved over the last decade. Decentralisation of DevOps, investment in platform capability and embracing product mentality has allowed organisations to:</p><ul><li>reduce dependency on the central platform team</li><li>make it easy for teams to support operations and address operational challenges</li><li>enable teams to focus on business problems by offering platform as a service</li><li>reduce technology drift, uplift security and provide automated governance</li></ul><h3>How can Data Mesh help?</h3><p>Data Mesh at core embraces decentralisation to unlock data value at scale by embracing these principals</p><ul><li>Domain ownership of data</li><li>Data as product</li><li>self-service data infrastructure as a platform</li><li>federated computational governance</li></ul><p>I would highly recommend reading more about these principles <a href="https://martinfowler.com/articles/data-mesh-principles.html">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*aQQ4cCFHcJxOQYzoZ4M0sw.png" /><figcaption>Decentralised Model</figcaption></figure><p>The key takeaway here is for organisations to <strong>invest</strong> in data infrastructure as a platform, to make it <strong>easier</strong> and <strong>cheaper</strong> for domain-aligned teams to produce their own data products and insights. Applying the platform thinking is critical to ensure</p><ul><li>capabilities are built for self-service</li><li>it reduces technology drift</li><li>best practices &amp; governance are part of the tooling</li></ul><p>SaaS data platforms like Snowflake are making it easier to democratise and decentralise data by having granular access controls, data masking, clean rooms to share data and offering new data stores like <a href="https://www.analytics.today/blog/snowflake-unistore-and-hybrid-tables"><em>Unistore</em></a> which can handle OLTP and OLAP workloads through the same store.</p><p>We believe a good self-service platform will allow engineers in domain-aligned teams to build data products without investing heavily in building new skill sets. This also gets us closer to self-service analytics where product owners, engineers and analysts of domain-aligned teams can write SQL queries to get their insights and have access to tooling to build dashboards.</p><p>If you are embracing to be a data-driven organisation, a cultural shift in thinking is required to prioritise investment and buy-in from senior leadership. Teams need to ensure they have the capacity &amp; skills, while product/delivery needs to prioritise producing data products so it is not an afterthought.</p><p>The closer we get to enabling the teams, the less cycle time from <em>data</em> &gt; <em>insight</em> &gt; <em>action</em> and organisations will see ROI as they unlock value for business and customers faster.</p><p>We plan to share more in upcoming blogs on how our journey progresses and the learnings that come out of it.</p><h3>References</h3><ul><li><a href="https://martinfowler.com/articles/data-monolith-to-mesh.html">https://martinfowler.com/articles/data-monolith-to-mesh.html</a></li><li><a href="https://martinfowler.com/articles/data-mesh-principles.html">https://martinfowler.com/articles/data-mesh-principles.html</a></li><li><a href="https://www.thoughtworks.com/insights/articles/break-though-the-centralized-platform-bottlenecks-with-data-mesh">https://www.thoughtworks.com/insights/articles/break-though-the-centralized-platform-bottlenecks-with-data-mesh</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6b85bb09dfa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wesfarmers-onedigital/why-data-mesh-e6b85bb09dfa">Why Data Mesh?</a> was originally published in <a href="https://medium.com/wesfarmers-onedigital">Wesfarmers OneDigital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Platform Engineering Team]]></title>
            <link>https://gsmadan.medium.com/building-a-platform-engineering-team-d07872b9e220?source=rss-14c61b8a4ab7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d07872b9e220</guid>
            <category><![CDATA[platform-thinking]]></category>
            <category><![CDATA[engineering-team]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Gurnam Madan]]></dc:creator>
            <pubDate>Tue, 08 Jun 2021 15:08:08 GMT</pubDate>
            <atom:updated>2021-06-08T22:19:03.988Z</atom:updated>
            <content:encoded><![CDATA[<p>The adoption of cloud, DevOps and micro-services (or appropriately sized services) has increased productivity by reducing dependency on centralised infra and operations but on the other hand, has increased cognitive load and expectations from product/stream-aligned teams.</p><p>Engineers spend more time on solving cross-cutting concerns instead of focussing on customer problems. Teams also get constrained by not having all the skill sets to own the full application and operations. There is also divergence in management of crosscutting concerns, consistency, security and adoption of sensible defaults. This leads to other challenges with product handovers and rotation of people in different teams.</p><p>A lot of organisations have adopted having platform engineering teams to solve these challenges. I wanted to share my learnings from building and running a platform team, hopefully it resonates with what you have experienced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*psjuyR1409cssS_WZhSUBg.png" /></figure><ul><li><strong>Don’t make it another DevOps team</strong>, and don’t relabel existing infrastructure and operations as a platform.</li><li><strong>What is your platform? </strong>Define who your customers are and your platform. How are your platform offerings going to enable delivery, reduce lead time and complexity? Think in terms of building blocks, x-as-a-service and abstractions you want to offer. You will need other skills apart from engineering to have a successful platform.</li><li><strong>Define team’s purpose, </strong>It is crucial to define what the team’s purpose is and how does it align with the strategic intent of the organisation. The focus needs to be around enablement, acceleration, being the multiplying force, collaboration and guardrails.</li><li><strong>Empathy for Customers, </strong>it is important for platform teams to acknowledge that their clients/customers are sitting next to them and you are building the platform for their consumption. Understand what their pain points are and collaborate with them to build your platform. They should be playing a key role in defining your roadmap. I have seen platform teams fail when there is a lack of collaboration and focus on solving problems that are not important for their customers. Good developer experience and operation experience is key for success and adoption.</li><li><strong>Self Service, </strong>build your offerings with self-service in mind to not become the bottleneck and support scaling with new teams. Emphasis on API-Driven, automatic provisioning, bot flows (e.g. slack bots) and observability.</li><li><strong>Open Source, </strong>to ensure you have high engagement and better collaboration adopt an internal open source policy. Encourage and acknowledge all the contributions. As maturity increases and there is better support from organisation think about public open source to contribute back to the community.</li><li><strong>Adoption, </strong>your value proposition for the platform needs to be good so it is the obvious choice. As discussed above collaboration and developer experience play a big part in it. We also found having regular workshops during onboarding or need basis helped a lot with adoption and feedback to improve products. Sometimes more engaged interactions are required to build skills within the teams for adoption.</li><li><strong>Measure, </strong>like any other product, ensure you are capturing metrics on usage of your platform and other key metrics.</li><li><strong>Funding, </strong>this may be more relevant when building a new team. But ensure you are adopting a capacity funded model for platform teams. Treat it as any other build and run team which requires persistence to support your platform and customers.</li></ul><p>Please comment your insights as well, would love to know how you are tackling some of these challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d07872b9e220" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Role of Identity in a microservices architecture — Part 1]]></title>
            <link>https://gsmadan.medium.com/role-of-identity-in-a-microservices-architecture-part-1-c561bb4b3a5a?source=rss-14c61b8a4ab7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c561bb4b3a5a</guid>
            <category><![CDATA[authorisation]]></category>
            <category><![CDATA[okta]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Gurnam Madan]]></dc:creator>
            <pubDate>Tue, 01 Jun 2021 13:51:55 GMT</pubDate>
            <atom:updated>2021-06-02T07:26:57.366Z</atom:updated>
            <content:encoded><![CDATA[<h3>Role of Identity in a microservices architecture — Part 1</h3><p>Recently, I have been involved in rolling out Okta Identity platform and define best practices for authentication, authorisation, and other security aspects to move towards a zero-trust model in a financial organisation.</p><p>In this post, you will see how authentication fits in modern application architecture and some key areas of consideration.</p><h3><strong>Authentication</strong></h3><p>Authentication is the process of determining user identity. The result of authentication in an OIDC context is an ID Token. Most likely you would also be getting an access token if you plan to call APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*xUWAV90lFy6rIAVW4mIDPQ.png" /></figure><p>The above diagram is highlighting the authentication process and journey of access token in a microservice environment.</p><p>There are few things you need to consider when setting up authentication</p><ul><li><strong>Create separate client per application</strong> e.g. SPA, iOS app and Android app. Having separate client allows you to configure better security policies, manage blast radius, design better customer experience, configure token lifecycle appropriately and have better tracing &amp; logging segregation.</li><li><strong>Do not store the access token in session storage or local storage for SPA clients</strong>. Use <a href="https://auth0.com/docs/flows/authorization-code-flow-with-proof-key-for-code-exchange-pkce">PKCE</a> flow which is built on top of authorization code flow to cater for <a href="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-browser-based-apps-03">security issues</a>. Keep the token in memory or ideally in a HttpOnly cookie. Leverage the identity provider’s SDK to take care of the authentication and authorisation dance instead of building your own.</li><li><strong>Enable adaptive MFA</strong>, to keep bad actors away by adding friction. Define your rules based on privilege needs, confidence and risks.</li><li><strong>Turn on attack protection</strong>, most of the big identity platforms (okta, auth0, ping, etc..) have systems/mechanisms to keep bad actors away from your application. They also provide signals for threats or anomalies, which you can subscribe to analyse and take actions asynchronously. Ensure to capture these events in your log aggregation platform with appropriate meta-data to correlate so you don’t lose observability.</li><li><strong>Set expiry for access tokens</strong>, for each client application consider how long the token should be valid. It may be very different for SPA vs native apps as security exposure is very different.</li><li><strong>Cache access tokens, </strong>reduce unnecessary roundtrips that extend your application’s attack surface and optimize plan token limits (where applicable) by storing access tokens obtained from the authorization server. Rather than requesting a new token, use the cached token during future calls until it expires.</li><li><strong>Limit what you expose in your access token </strong>to external clients<strong> </strong>(ideally only primary identifier). If you need more information in the token for backend services, it should be enriched once the request is in your network boundary. Generally, API Gateway or middleware or sidecars are good places to do this. Don’t enrich your token with PII or other sensitive information.</li><li><strong>Validate your token</strong>, API Gateway is a good candidate to do this. Most of the gateways have integration available with modern Identity Providers to do this easily. Doing it at the gateway level allows you to ensure requests with invalid token are rejected before it reaches your application. In the case of M2M, you may choose to validate in middleware or sidecar or mesh proxy. Again, in a microservices environment observability is key, so ensure logs &amp; traces are captured and can be correlated.</li><li><strong>Ensure to embed the user token</strong> when a request is fanned out from external service to internal services. Generally, your internal services get called with a machine token, it is important to have user context to authorise appropriately.</li></ul><p>It is important to consult with platform, product, infosec and app sec teams to define authentication best practices and standards. This will enable product engineering teams to focus on solving customer problems and ensure consistent security policies and standards are applied to keep customer data safe.</p><p>In the next part, I will cover authorisation and coarse-grained access. Hopefully, you find some of these insights useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c561bb4b3a5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Distributed High Value Transaction Systems]]></title>
            <link>https://gsmadan.medium.com/building-distributed-high-value-transaction-systems-2076d5d757ad?source=rss-14c61b8a4ab7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2076d5d757ad</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[orchestration]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <dc:creator><![CDATA[Gurnam Madan]]></dc:creator>
            <pubDate>Thu, 04 Jun 2020 14:04:39 GMT</pubDate>
            <atom:updated>2020-06-04T21:08:37.407Z</atom:updated>
            <content:encoded><![CDATA[<p>Being in the financial industry for the past couple of years has allowed me the opportunity to work on some fairly complex systems. I want to share some insights gained whilst building and running these distributed systems.</p><p><strong>High Value Distributed Systems</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpXew5FWuUyfkpwkvvr1nw.png" /><figcaption>Distributed Systems</figcaption></figure><p>Let’s define some of the characteristics of these systems</p><ul><li>Transaction value from customer or business prospective is high e.g revenue loss or customer trust.</li><li>Transactions of these natures are generally highly regulated from compliance, security or governance perspective.</li><li>Transactions are distributed in nature, requires multiple actors to do their jobs for it to be successful.</li><li>Transactions may be long-lived.</li></ul><p>Loan Origination or Payment systems are good examples of this in the financial domain.</p><p><strong>Build Approach</strong></p><p>Let’s take a simplified example of a credit card application, which goes through multiple steps before customers application can be approved or rejected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*bvfEr0YBM0lXGsdvbvC-DA.png" /></figure><p>Adopting micro-services or as I like to call <em>“appropriately sized services”</em> will allow us to build services which are:</p><ul><li>Loosely coupled</li><li>Follow the single responsibility principle</li><li>Independently Deployable</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*-SkioC7Sk9UwXuT0FC7QSQ.png" /><figcaption>Actors — Independent Services</figcaption></figure><p>Typically teams adopt <strong>choreographed architecture </strong>as they move towards micro-services (based on Martin Fowler’s <a href="https://martinfowler.com/articles/microservices.html">article</a>). This generally gets combined with event-driven architecture to reduce temporal coupling.</p><p>Domain events are emitted and interested parties act upon them. This allows for adding new consumers/services without changing anything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*86ZZ91mGcJ02q4w61VnnNA.png" /><figcaption>Domain Events</figcaption></figure><p>The workflow is not explicitly defined but is represented as a chain of events.</p><p>In this state, the system looks well designed with all the goodness of micro-services and event-driven architecture, but poses a big concern.</p><p>In this architecture where each micro-service is designed to be responsible for a particular scope, <strong><em>who looks after the end to end workflow?</em></strong></p><p>No one, what we have here is a peer-to-peer chain of events which implicitly defines flow in code distributed across services.</p><p>Choreography does not cater well for two aspects:</p><ul><li><strong>Visibility — </strong>It will be very hard for us to answer questions like “<em>How many pending applications?</em>”, “<em>why is the application pending?</em>” and “<em>What is the average time to complete an application?</em>”</li></ul><p>Some of this can be mitigated by introducing distributed tracing and logging, but generally is not enough and becomes complicated as we are treating the symptom and not the cause.</p><ul><li><strong>Fault Tolerance — </strong>How do we ensure the state is consistent or the workflow completes in an error scenario. Applying compensating transactions can become complicated in choreographed architecture.</li></ul><p>There is a third issue which creeps in as we evolve our solution, what if in the context of our example we wanted to do Identity Verification and Income Verification in parallel. That would lead to changing subscription for some services and introduce co-ordination between them. This becomes worse if teams managing those services are different.</p><p><strong>Orchestration to rescue</strong></p><p>Orchestration helps to take responsibility for the end-to-end workflow and provide guarantees around fault tolerance to manage prolonged downstream failures. <a href="https://microservices.io/patterns/data/saga.html">Saga pattern</a> allows us to apply the compensations to maintain consistency, even for long running processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*xzi7mjFxI_wMq4tDT3jWcA.png" /><figcaption>Orchestration — Saga Pattern</figcaption></figure><p>Workflow engines can help in building this orchestration layer using state machine with saga pattern. They can address all the concerns we discussed earlier around visibility and fault tolerance.</p><p>Generally, there is an opinion to avoid workflow engines due to scalability concerns and centralised nature. But there are some good workflow engines available where teams have been able to alleviate these concerns and still do all the heavy lifting required to manage workflows.</p><ul><li><a href="https://aws.amazon.com/step-functions/">AWS Step Functions</a> — Step functions have come a long way in terms of maturity and is a good cloud native serverless option which can help to build and manage workflows at scale. We have been using them largely to build simple workflows.</li><li><a href="https://cadenceworkflow.io/">Uber Cadence</a> — Built and open sourced by the Uber engineering team, probably one of the best platforms which trying to solve these concerns. We are currently spiking it out to deal with some our complex workflows which have complex branching and decision-making.</li></ul><p>Some other options which I have not spent too much time exploring, but look equally interesting are:</p><ul><li><a href="https://netflix.github.io/conductor/">Netflix Conductor</a></li><li><a href="https://zeebe.io/">Camunda Zeebe</a></li></ul><p><strong>Recommendation</strong></p><p>A well-architected solution generally will have orchestration and choreography in the mix. It requires experience and domain knowledge to manage the balance between commands and events. And understand the trade-offs in the context of key characteristics of the systems. In this case, it was <strong>high value </strong>transactions than <strong>high volume.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2076d5d757ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Observability as Code — DataDog]]></title>
            <link>https://gsmadan.medium.com/observability-as-code-datadog-ce407fb8bc30?source=rss-14c61b8a4ab7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce407fb8bc30</guid>
            <category><![CDATA[datadog]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <dc:creator><![CDATA[Gurnam Madan]]></dc:creator>
            <pubDate>Mon, 02 Sep 2019 11:43:46 GMT</pubDate>
            <atom:updated>2019-09-02T11:43:46.458Z</atom:updated>
            <content:encoded><![CDATA[<h3>Observability as Code — DataDog</h3><p>At Latitude Financial Services we have been focusing on improving the observability of our distributed systems; to have consistency and reduce time to instrument metrics, tracing, dashboards, monitors and alerts for our appropriately sized services.</p><p>Teams were doing repetitive tasks to set-up observability for their services. Changes were made over time to dashboards, monitors, and alerts but reasons were not being captured anywhere.</p><p>Thoughtworks featured <a href="https://www.thoughtworks.com/radar/techniques/observability-as-code">observability as code</a> in their 2018 tech radar highlighting these concerns and how treating these configurations as code can address the issue.</p><p>At Latitude, we use DataDog for our application and infrastructure monitoring. We could not find any suitable tools for managing DataDog dashboards and monitors. Hence we decided to build our own tool <strong>Growl</strong>.</p><p>Growl uses DataDog APIs to manage dashboards and monitors. The first version has the following features:</p><ul><li>Create and edit time-boards and monitors.</li><li>CLI interface for CI/CD integration.</li><li>Golang library for dynamically generating dashboards and alerts. Primarily used by our cloud team when they provision infrastructure for tenants.</li><li>Capability to dynamically introduce variables and tags like service name, environment and domain.</li><li>Local developer experience to create changes and export it back as configuration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*RkGeNGEPXnFspbP6lsb5pw.png" /><figcaption>Dashboard management life cycle</figcaption></figure><p>Our service starter kit provides developers standard dashboards and monitors. So they are part of the source code from day one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ltMplXBCAiLp5Sa4hpSHTw.png" /><figcaption>Standard health dashboard created by Growl</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rmPmG1EH4fTcUfG9VnSMvA.png" /><figcaption>Standard monitors created by Growl</figcaption></figure><p>Any changes made dashboards or monitors get captured through github commits and pull requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-xu1VUtAbPO5KbjyOozhmA.png" /><figcaption>Github pull request example</figcaption></figure><p>To ensure users don’t edit these dashboards or monitors manually, they are locked to be only modified by the creator i.e. Growl.</p><p>By treating these configurations as code and embracing naming &amp; tagging conventions, we are saving developers hours of effort and introducing better practices and consistency.</p><p>Next steps for us to include relevant infrastructure metrics and potentially look at making Growl open source.</p><p>We are always on the lookout for good engineers to join our team, please feel free to reach out if you want to know more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce407fb8bc30" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>