<?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 Suman Upadhyay on Medium]]></title>
        <description><![CDATA[Stories by Suman Upadhyay on Medium]]></description>
        <link>https://medium.com/@suman.upa?source=rss-e5723ff96ac2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-4tlpzyDmD5sgSw5XRlv3w.jpeg</url>
            <title>Stories by Suman Upadhyay on Medium</title>
            <link>https://medium.com/@suman.upa?source=rss-e5723ff96ac2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:15:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@suman.upa/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[Vibe Coding -Enhancing Product Clarity via Rapid Prototyping]]></title>
            <link>https://medium.com/@suman.upa/vibe-coding-enhancing-product-clarity-via-rapid-prototyping-85269a1db636?source=rss-e5723ff96ac2------2</link>
            <guid isPermaLink="false">https://medium.com/p/85269a1db636</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[copilot-programming]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <dc:creator><![CDATA[Suman Upadhyay]]></dc:creator>
            <pubDate>Tue, 15 Jul 2025 02:20:51 GMT</pubDate>
            <atom:updated>2025-07-15T02:38:07.155Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Vibe Coding -Enhancing Product Clarity via Rapid Prototyping" src="https://cdn-images-1.medium.com/max/1024/0*hjuuNfDzydJ0t9hK" /><figcaption>Photo by <a href="https://unsplash.com/@ikukevk?utm_source=medium&amp;utm_medium=referral">Kevin Ku</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve always believed in writing things down — PRDs, flow diagrams, Confluence docs, User Journey. But sometimes, even the most thoughtful planning and writing can leave your vision feeling abstract. That was exactly where I found myself: with an idea I cared about, but lacked visual illustration and its behavior from a user perspective.</p><p>Rapid prototyping isn’t a new concept — designers, engineers, and builders have relied on it for years. But what I tried recently as a product manager wasn’t about validating an MVP. It was about enhancing product clarity through building, before anything made it to the roadmap.</p><p><strong>So I tried something new.</strong></p><p>In a short period, I used vibe coding to build a working prototype — complete with a frontend UI, two backend Spring Boot services, and an AI agent powered by GPT-4. The result? A level of product clarity I couldn’t have reached through PRD alone.</p><p><a href="https://www.klover.ai/andrej-karpathy-vibe-coding/"><strong>What Is Vibe Coding?</strong></a></p><p>​​The term vibe coding was popularized by<a href="https://www.klover.ai/andrej-karpathy-vibe-coding/"> Andrej Karpathy</a>, who described it as giving in to the creative flow and using AI to help translate intent into code. For a product Manager, it is the practice of rapidly building just enough to explore your product idea. It’s not about shipping polished apps. It’s about reducing the distance between vision and working experience — through lightweight, expressive, hands-on prototypes. It’s how product managers can quickly move from “I think this could work” to “I can now see how it flows, feels, and might break.”</p><p><strong>A 4-Day Journey from Idea to Experience</strong></p><p>Day 1- I focused on writing a one-pager PRD — defining the high-level goal, mapping flows, and outlining unknowns. But the vision still felt abstract.</p><p>Day 2- I mocked up a simple React-based chat UI in<a href="https://replit.com/"> Replit</a>, simulating how users might interact with the system. It helped me visualize the flow, design, and pacing of interactions.</p><p>Day 3- I built the first backend: a Spring Boot middleware app with REST APIs, scaffolded using<a href="https://github.com/features/copilot"> Copilot</a>. This layer handled UI input, generated mock data, and forwarded prompt requests to the AI service.</p><p>Day 4-I built a second Spring Boot service — the AI Agent. This backend called GPT-4, applied lightweight logic to interpret the response, and returned a structured output to the middleware.</p><p>These tools helped me move quickly from idea to interaction, as a way to clarify the product vision, test assumptions, and enable more meaningful collaboration with the tech team. The goal wasn’t to build production code, but to ensure that when the time came to build, I could partner with engineering from a place of deeper understanding.</p><p><strong>By the end of Day 4, I had a complete prototype loop:</strong></p><ul><li>A user enters a prompt in the chat UI</li><li>The middleware backend receives the input and sends it to the AI service</li><li>The AI Agent backend calls GPT-4, applies lightweight logic to interpret the response, and returns a structured output to the middleware</li><li>The frontend displays the response in real time</li></ul><p>Code wasn’t build to ship — but it was real enough to validate the end-to-end experience and clarify what needed to be built.</p><p><strong>Why Vibe Coding Matters for Product Managers</strong></p><ul><li><strong>Clarity Through Experience</strong>- You don’t fully understand a product until you interact with it. Diagrams and documents are useful — but prototypes bring ideas to life in ways that highlight blind spots, friction, and value.</li><li><strong>Faster Feasibility Checks</strong>- Rather than speculating about system behavior or user flow, I could test it. Even with mock logic and simplified assumptions, the prototype helped me uncover implementation constraints early.</li><li><strong>Better Conversations with Engineers</strong>- With a working prototype, I could communicate intent more precisely, walk through examples, and gather technical input with greater context.</li><li><strong>Visualizing for Design and UX</strong>-Mocking the frontend helped me better understand pacing, layout, and interaction.</li></ul><p><strong>Key Takeaways</strong></p><p>Vibe coding isn’t about doing it all — it’s about thinking like a builder and partnering more effectively with those who bring product vision to life.</p><p>It enables Product Managers to:</p><ul><li>Explore ideas with lower cost and risk</li><li>Validate direction before committing to implementation</li><li>Sharpen their understanding of technical architecture</li><li>Collaborate more effectively across design, product, and engineering</li><li>Create alignment grounded in interaction, not just documentation</li></ul><p>This 4-day prototype sprint didn’t just help me document an idea — it helped me understand it. That clarity shaped every conversation that followed: with engineering, with design, with leadership.</p><p>So if you’re a PM with a half-formed idea and a ton of open questions, don’t wait for a sprint or a wireframe.</p><p>Start small. Build something scrappy. Feel it. Break it. Fix it.<br>And then — when it’s time to build — you’ll be ready to lead with confidence and clarity — So, <strong><em>Build to understand. Understand to lead.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85269a1db636" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating the Shift: From Software Development to Product Management]]></title>
            <link>https://medium.com/@suman.upa/navigating-the-shift-from-software-development-to-product-management-9d74515fe9f3?source=rss-e5723ff96ac2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d74515fe9f3</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Suman Upadhyay]]></dc:creator>
            <pubDate>Mon, 10 Jul 2023 03:27:57 GMT</pubDate>
            <atom:updated>2023-07-10T03:27:57.137Z</atom:updated>
            <content:encoded><![CDATA[<p>A few years ago, in the coziness of my office cubicle, where coding syntax was the universal language, I found my natural habitat. My domain was the intricate universe of Java, where my days were spent wrangling elusive software bugs, deciphering the riddles of JAR file version compatibility, and intercepting notorious NullPointerExceptions.My victories were accompanied by the shimmer in my eyes at the launch of a new version of Eclipse IDE and the gratifying sigh of relief when integrations with third-party software systems fell seamlessly into place. However, an unanticipated opportunity struck a chord, enticing me towards a different rhythm — transitioning into a Technical Product Manager.</p><p>Switching careers isn’t as straightforward as changing IDEs; it’s akin to swapping a keyboard for a compass mid-voyage. The transition was gradual, mirroring the iterative refinement of a Java program rather than an abrupt leap.</p><p>Immersed in a product I helped develop, my role expanded from building features to steering the product’s daily operations. My increasing intimacy with the application and its peripheral elements fostered a sense of ownership, gradually elevating me to a subject matter expert. Over time, my expertise started molding the product’s roadmap, from minor features to its overarching direction.</p><p>This evolution of my role was not a sudden metamorphosis but a gradual process. It was akin to building an application — piece by piece, steadily, and ultimately culminating in a gratifying sense of achievement. Amidst this process, I acquired a holistic understanding of the business and our product’s unique place within it, further enriching my journey from software developer to Technical Product Manager.</p><h3>Similarities: More Than What Meets the Eye</h3><p>Despite the apparent divergence between a Software Developer and Product Manager roles, they share some striking parallels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-SswcD8V6noX1rc0yMabA.png" /><figcaption>Similarities</figcaption></figure><ul><li><strong>Problem Solving:</strong> As a senior technologist, bugs were challenging puzzles. Tackling them honed my problem-solving skills. In product management, problem-solving stayed; only the bugs were replaced with challenges spanning from product features to stakeholder management. Problem solving remained constant.</li><li><strong>Adaptability</strong>: Embracing the Change: If changing project requirements were daunting as a developer, as a Product Manager, they were on hyperdrive. Market trends, customer preferences, and business strategies were continually evolving, making adaptability crucial — a trait that I honed during my coding days.</li><li><strong>Technology</strong>: My profound technical understanding, a result of many battles with Java, became a superpower in product management, bridging the gap between technical and non-technical folks, setting realistic expectations, and understanding feature feasibility.</li><li><strong>Continuous improvement</strong>: The quest for cleaner, efficient code in development echoed in product management, where there was always something to improve.</li><li><strong>Iterative Approach</strong>: Software development follows an incremental, iterative approach, as does product development — a familiar and comfortable strategy in my new role.</li><li><strong>Collaborative Nature</strong>: Both roles necessitate collaboration, albeit with different teams and towards different goals. As a developer, I worked with other developers, designers, and sometimes operations to deliver a product. As a product manager, I coordinate with similar teams but also communicate extensively with business stakeholders and customers, integrating their input into the product strategy.</li><li><strong>Goal-Oriented</strong>: Both roles require a goal-oriented mindset. As a developer, the goal was to solve a problem or create a feature within specified constraints. As a product manager, I aim to align the product strategy with business objectives, while also meeting the needs of our users.</li></ul><h3>Discovering the Differences: A Whole New World</h3><p>Despite the common ground, the transition wasn’t merely about a change in job title; it brought along an entirely different perspective.See the list of differences in the diagram below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ArafRH6uNKLEzu6o" /><figcaption>Differences</figcaption></figure><ul><li><strong>Coding vs Communicating</strong>: From dialoguing with software, my conversations shifted to humans, involving a more complex and nuanced language.</li><li><strong>Building vs Guiding</strong>: I transitioned from building to guiding — charting the path, defining what to build, and outlining the timelines.</li><li><strong>Depth vs Breadth</strong>: The focus shifted from deep-diving into codebases to needing a panoramic view of an entire landscape, including market trends, user needs, and business models and top down organizational vision.</li><li><strong>Micro vs Macro</strong>: The lens zoomed out from micro-details like code quality to macro considerations like business strategy, user experience and organizational goal alignments.</li><li><strong>How-When Vs What-Why:</strong> As a developer, my focus was on ‘how’ and ‘when’. Now, as a Product Manager, my lens has shifted to the ‘what’ and ‘why’, demanding a more strategic approach to product decision-making.</li><li><strong>Stakeholder Management:</strong> As a developer, my key stakeholders were mostly internal: the product team, QA, and on occasion, design. As a Product Manager, I engage with a broader set of stakeholders: customers, sales, marketing, senior management, and more, with each group having its own set of needs and communication styles.</li><li><strong>Risk Management</strong>: As a developer, I was focused on technical risks such as bugs, software incompatibilities, and code debt. As a product manager, I must manage broader product and business risks: market competition, customer satisfaction, business alignment, and overall return on investment.</li></ul><h3>The Learning Curve: New Skills for a New Role</h3><p>In my transition to product management, I pursued certifications such as Scrum Master, Product Owner, and Product Manager to bolster my knowledge. While these offered valuable theoretical insights, I found that on-the-job learning was the most effective way to immerse myself in the new role. Practical experience, dealing with real-world scenarios, proved to be an incredible accelerator.</p><p>The transition also demanded new skills beyond my developer toolkit.These skills are not something that one can acquire overnight. Learning is a continuous journey, and I am becoming better every day, step by step, much like improving upon a piece of code with each iteration.</p><ul><li><strong>Strategic Thinking</strong>: Grasping business strategy became vital, requiring an understanding of market dynamics, competitive landscapes, and customer behavior patterns.</li><li><strong>Communication</strong>: Articulating ideas, mediating discussions, and making persuasive presentations became a regular part of my routine. It’s an ongoing learning process, with every interaction providing opportunities for refinement.</li><li><strong>Leadership</strong>: Managing a product involves leading cross-functional teams, demanding skills in leadership, negotiation, and conflict resolution.</li><li><strong>User Empathy</strong>: Having a user-centric approach was crucial. I needed to empathize with users, understand their needs, and incorporate that perspective into product decisions.</li><li><strong>Data-Driven Decisions</strong>: Being comfortable with data and deriving meaningful insights from it became as crucial as deciphering a tricky piece of Java code.</li><li><strong>Project Management</strong>: As a product manager, it became important to acquire project management skills. Being able to define goals, plan effectively, manage resources, and keep projects on track while dealing with uncertainties and risks is as crucial as writing effective code.</li><li><strong>Market Research:</strong> Understanding the competitive landscape, customer preferences, and trends became essential. Much like debugging a program, identifying the needs and behaviors of users in the market helps define the right product strategy.</li></ul><h3>What to Watch Out For</h3><p>Transitioning from Software Development to a Product Manager can be an exciting journey filled with immense learning and growth. However, it’s essential to be aware of the potential pitfalls that can hinder this journey. Recognizing and navigating these common mistakes can empower Software Developers to transition smoothly and effectively into successful Product Managers. Here are some pitfalls to consider:</p><ul><li><strong>Solutioning</strong>: A technologist turned Product Manager might be tempted to jump straight into solution mode instead of taking the time to fully understand the problem. It’s crucial to remember that a significant part of a Product Manager’s role is to define the problem and validate it before jumping to solutions.</li><li><strong>Neglecting the non-technical aspects</strong>: It’s easy to focus heavily on the product’s technical aspects, forgetting that product management involves understanding the business strategy, market dynamics, and customer behavior.</li><li><strong>Technical Communication</strong>: Given a technologist’s background, there’s a tendency to communicate in a manner that’s too technical for some stakeholders. It’s essential to adjust the level of technical detail according to the audience.</li><li><strong>Overlooking User Experience</strong>: A deep understanding of technology can sometimes cause a bias towards what’s technically impressive rather than what provides the best user experience. It’s essential to maintain a balance.</li><li><strong>Underestimating the Importance of Soft Skills</strong>: Technical skills are crucial, but product management also requires significant soft skills like leadership, negotiation, and communication. These should not be undervalued and a product manager must remember to nurture them.</li></ul><h3>My Verdict: A Journey Worth Taking</h3><p>Shifting from Software Development to Technical Product Management was an exhilarating chapter, filled with fresh learning, challenges, and triumphs. Like an orchestra conductor, I found myself synchronizing varied sections to compose a harmonious symphony in this new role.</p><p>For those contemplating a similar journey, know that the grass on the other side is indeed a different shade. However, it offers its unique blend of challenges and opportunities. If you relish solving complex problems, navigating intricate dynamics, and are open to trading your debug logs for strategizing a product vision, and defining its life cycle, this transition might be the adventure you’ve been waiting for.</p><p>So, here’s to embracing challenges, charting unexplored territories, and enjoying the roller coaster ride that is the transition from coding to product management. It’s different and challenging, but every bit worth it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d74515fe9f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Changing Lanes: Navigating from Monitoring to Observability]]></title>
            <link>https://medium.com/@suman.upa/changing-lanes-navigating-from-monitoring-to-observability-bcded62c5f77?source=rss-e5723ff96ac2------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcded62c5f77</guid>
            <dc:creator><![CDATA[Suman Upadhyay]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 11:51:18 GMT</pubDate>
            <atom:updated>2023-07-07T11:51:18.841Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E5KanymBzJwyc7XZ" /></figure><p>In the world of IT and software development, monitoring and observability are two terms that are often used interchangeably. However, they are not the same thing. In fact, they serve different purposes and require different approaches. In today’s blog, let us explore the differences between monitoring and observability, and why it matters.</p><p><strong><em>Monitoring tells you whether the system is working. Observability lets you ask why it is not working</em></strong> — Baron Schwarz</p><p><strong>Monitoring: </strong>It is the ability to gather and observe data from systems to determine its status. It is passive consumption of information from systems to determine state and status. It alerts on thresholds set on metrics for the state of systems and relies on humans to respond. It contains tools that are purpose built for static systems and platforms and don’t change much over time. In Complex systems monitoring alone does very little</p><p><strong>Observability: </strong>It is a newer concept that takes monitoring to the next level. In fact, it encompasses monitoring. Observability provides visibility into the internal state of a system or application, allowing for faster and more effective troubleshooting. It holistically considers all data from systems being managed to determine a proactive and automated response. It continuously improves on how systems are observed, tuned and fixed using automation. It contains tools that are purpose built for dynamic systems and platforms that widely change in complexity.</p><p>Picture this: You are driving your trusty car down the highway. You rely on metrics such as fuel level, engine temperature, speedometer, oil level to tell you what you need to know about your car running smoothly. However an unexpected peculiar noise from under the hood leaves you perplexed and stranded. You have no idea what is going on, it takes you much longer to resolve the issue, maybe even requires a trip to the mechanic shop. This scenario epitomizes traditional monitoring in a nutshell. It is like driving with blinders on, relying on a few predefined metrics to give you a sense of the system’s health. All is well until an unexpected problem arises and then you are left scrambling for answers.</p><p>Now envision yourself in a cutting-edge modern car furnished with sensors and AI-driven diagnostic systems that can foresee potential problems before they materialize. And even if problems do arise, you receive contextual data that illuminates the what, why and how of the situation, along with actionable insights for swift resolution. No more getting stranded on the highway, at least not for too long or even better if the sensors could predict damage and stop by the nearest mechanic instead of stopping a mile or 2 later, when it’s too late that the car cannot move anymore. This illustration captures the essence of modern observability — a comprehensive, adaptable and modern approach that enables holistic understanding of the system’s behavior and thus empowering you to see the bigger picture and act accordingly.</p><p>While both monitoring and observability rely on system data to fix issues, there are significant differences between the two.</p><p><strong>1) Simple Data vs Actionable Insights</strong></p><ul><li>With Monitoring you get simple data that has binary outcome, if an issue exists or not. Often the focus is on collecting and alerting on data, mainly metrics and logs. After receiving the alerts/signals, SRE’s carry out manual investigation, correlation and root cause analysis.</li><li>Observability focusses on collecting wide range of data, including logs, metrics, traces. It helps analyze, correlate and provide context to the data thus providing actionable insights. In case of complex systems visibility into system wide data pool can help facilitate faster root cause analysis.</li></ul><p><strong>2) Known Unknowns vs Unknown Unknowns</strong></p><ul><li>Scope of monitoring is limited to predefined metrics and threshold to determine system availability and performance. This gives limited insight into systems health. But what if a problem arises that is not being tracked by predefined set of metrics?.</li><li>In case of observability dynamic, flexible data is gathered from entire system that helps zero in on a problem. The focus is on getting insight into overall health of the system from the available telemetry thus providing holistic view of the entire system and associated components.</li></ul><p><strong>3) Reactive vs Proactive</strong></p><ul><li>Monitoring relies on predefined system outputs and alerts you when the values go out of threshold. Monitoring focusses on symptoms and hence takes reactive approach.</li><li>Observability enables you to take preventive action via system wide data collection and analysis. It helps uncover hidden issues, new patterns, unexpected problems and complexities not captured by predefined metrics. Observability focusses on root cause and takes proactive approach.</li></ul><p><strong>4) Operations-focused users vs Comprehensive users</strong></p><ul><li>Monitoring caters more specifically to operation focused audience that includes DevOps, Production Management, System Admin, SRE.</li><li>Observability encompasses a broader range of stakeholders including SRE, Production Support, Application team, DevOps, QA Testers, Business teams, Management Executives</li></ul><p>A few years ago, when I was a developer, I experienced firsthand the challenges of monitoring complex systems. Back then monitoring was primarily the domain of DevOps engineers/System Admins, not developers. It often felt like we were operating in silos, with developers focusing on developing and maintaining applications, while DevOps Engineers were responsible for ensuring their performance and availability. Known metrics based on rate, error, latency was established and then the team would respond when apps crashed or underperformed. This strategy relied on recognized metrics to generate alerts for unforeseen circumstances. The unknown remained shrouded in mystery, exemplifying a highly reactive approach.</p><p>However, as the shift-left approach gained traction, the boundaries began to blur, thus emphasizing the need for early and continuous involvement of developers, DevOps and SRE’s. Consequently, Observability has become an essential aspect of application development, requiring developers to instrument their systems that emit telemetry data, making it easier to understand and monitor the system behavior. This approach thus allows for a proactive approach, lifting the veil on the unknowns that were once shrouded in mystery.</p><p>Have you ever seen a pilot navigating the clouds looking out of the window.? Of course not!!!. The intricate world of aviation demands advanced instruments, sensors and automation to ensure safe, smooth flight. Similarly, we should now turn to observability to help navigate the modern complex , dynamic and distributed systems. As we embrace observability, we should welcome automation, contextual data, predictive analysis and holistic understanding that observability offers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcded62c5f77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Dive into the Language of SRE and Observability: Key Terms Demystified]]></title>
            <link>https://medium.com/@suman.upa/a-dive-into-the-language-of-sre-and-observability-key-terms-demystified-44ae7827e76c?source=rss-e5723ff96ac2------2</link>
            <guid isPermaLink="false">https://medium.com/p/44ae7827e76c</guid>
            <dc:creator><![CDATA[Suman Upadhyay]]></dc:creator>
            <pubDate>Wed, 05 Jul 2023 20:45:30 GMT</pubDate>
            <atom:updated>2023-07-05T21:24:58.887Z</atom:updated>
            <content:encoded><![CDATA[<p>In the ever-evolving world of software, two concepts have risen to prominence due to their pivotal role in enhancing system reliability and performance: Site Reliability Engineering (SRE) and Observability. These disciplines have reshaped the landscape of IT operations, introducing practices and ideologies that ensure smooth service delivery and optimal user experiences.</p><p>This blog explores key terminologies and foundational concepts in SRE and Observability. Whether you are a newcomer stepping into these domains or an established professional seeking a renewed perspective, our aim is to provide an enriching educational resource by carefully unraveling each term and demonstrating its relevance within the larger schema.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KRx2qJTOw1r2QYZ3ajaHWQ.jpeg" /></figure><p><strong>Site Reliability Engineering (SRE): </strong>Bridging the Gap between Development and Operations.</p><p>Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems. The main goals are to create scalable and highly reliable software systems.</p><p>When we think about SRE, we begin with the intention of creating reliable systems. We use Service Level Indicators (SLIs) to measure the performance, set targets through Service Level Objectives (SLOs), and then make formal agreements with users via Service Level Agreements (SLAs).</p><p>We understand that innovation often involves taking risks, which is why we work with an Error Budget. It gives us room to make mistakes and learn without impacting reliability. When things do go wrong, we don’t point fingers. Instead, we conduct a Blameless Postmortem to learn and improve our systems.</p><ul><li><strong>Incident Management: </strong>Incident management is crucial in SRE as it involves preparing for and responding to system failures and disruptions, ensuring quick recovery and minimizing damage.</li><li><strong>Reliability: </strong>This refers to a system’s ability to function consistently and accurately over time.</li><li><strong>Service Level Indicators (SLIs):</strong> Quantitative measures of some aspects of the level of service, defined and measured according to user experience.</li><li><strong>Service Level Objectives (SLOs):</strong> Target values for service level performance, typically based on customer requirements and expectations.</li><li><strong>Service Level Agreements (SLAs):</strong> Explicit contracts outlining the service level performance a customer can expect.</li><li><strong>Error Budget:</strong> This is a concept that balances the need for rapid innovation and reliable service. It quantifies the acceptable level of errors in a system.</li><li><strong>Toil:</strong> Repetitive operational work offering no lasting value and scaling linearly with service growth.</li><li><strong>Blameless Postmortem:</strong> This is a process where a team examines a system failure with an aim to understand and correct the underlying issues that caused the incident, rather than assigning blame.</li></ul><p><strong>Observability:</strong> Understanding System Performance</p><p>Observability is an attribute of a system that determines whether its internal states can be inferred by only looking at its external outputs. It’s a crucial aspect of system design for detecting and diagnosing problems.</p><p>In the world of Observability, we use three main tools, often referred to as the Three Pillars of Observability: Metrics, Logs, and Traces.In this process, Events stand out as important occurrences in the system. Latency, Availability, and Throughput are specific types of Metrics that are vital in monitoring system performance.Telemetry is another key concept in this space. It involves sending data back for analysis. With different types of data, we can do a Correlated Telemetry analysis for a more comprehensive understanding of system performance.</p><p>Alerts help us identify when something’s not right and need immediate attention. But these aren’t just any alerts. They are In-Context Alerts, providing us with the relevant information for quicker resolution. Notifications also play a vital role, keeping us informed about changes or events in the system.Cross-Account Observability allows us to view and monitor multiple accounts or entities in a system, which is particularly important in larger setups.Meanwhile, Dependency Mapping allows us to visually comprehend the relationships between various services in the system. Finally, we use Monitors and Dashboards to keep an eye on the system’s data and metrics over time, giving us a visual and real-time view of system performance.</p><ul><li><strong>Three Pillars of Observability:</strong> Metrics, Logs, and Traces are often referred to as the “Three Pillars of Observability.” They provide the data that teams need to understand their systems.</li><li><strong>Instrumentation: </strong>Adding capabilities to the system and application to track and capture data that can be used to observe the behavior and performance.</li><li><strong>Metrics:</strong> These are numerical data that represent the state of a system at a point in time.</li><li><strong>Logs:</strong> These are time-stamped records of events that occur in a system.</li><li><strong>Traces: </strong>These provide detailed information about operations that a system performs to service a particular request.</li><li><strong>Events:</strong> These are discrete actions or changes that occur in a system.</li><li><strong>Golden Signals: </strong>Latency, traffic, error rate, resource saturation are the four key metrics often tracked in observability practices to understand system performance.</li><li><strong>Anomaly Detection: </strong>This is the identification of data or behavior that deviates from an expected pattern.</li><li><strong>Cross-Account Observability:</strong> This involves observing and monitoring multiple accounts or entities in a system.</li><li><strong>Dependency Mapping:</strong> This is an important practice in building observable systems, as understanding dependencies can aid in diagnosing issues.</li><li><strong>Telemetry:</strong> This is the process of recording and transmitting data from monitoring systems to aid in remote diagnosis and troubleshooting.</li><li><strong>Correlated Telemetry:</strong> This refers to the collective analysis of different types of telemetry data to gain a more comprehensive understanding of system performance.</li><li><strong>In-Context Alerts:</strong> These are alert notifications with relevant contextual information, aiding in quicker diagnosis and resolution.</li><li><strong>Notifications: </strong>These are alerts or messages that inform users about the changes or events within a system.</li><li><strong>Alerts: </strong>These are notifications that indicate when a system has reached a defined threshold, requiring immediate action.</li><li><strong>Monitors: </strong>These are tools or devices that track and display information about a system over time.</li><li><strong>Dashboards:</strong> Visual interfaces aggregating and illustrating data and metrics in an easily digestible format.</li></ul><p>The expansive realms of SRE and Observability, with their inherent complexity, present great opportunities for innovation and performance optimization. As these disciplines evolve, they will continue to introduce new terms and concepts. Keeping pace with the latest trends and engaging in continuous learning is therefore crucial for anyone involved in these sectors. I trust that this glossary will prove a valuable resource, offering clarity and insight into the intricate landscapes of SRE and Observability. As you journey further into these domains, I hope you find not just understanding, but also inspiration, at the cutting edge of technology.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44ae7827e76c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>