<?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 Niranjan Kumar on Medium]]></title>
        <description><![CDATA[Stories by Niranjan Kumar on Medium]]></description>
        <link>https://medium.com/@niks4one?source=rss-afe0ab1a92ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y1hZ3CEu3PF5A2URGOt0gg.jpeg</url>
            <title>Stories by Niranjan Kumar on Medium</title>
            <link>https://medium.com/@niks4one?source=rss-afe0ab1a92ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:33:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@niks4one/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[Enabling Real-Time Business Monitoring with Klaxon]]></title>
            <link>https://medium.com/swiggy-bytes/enabling-real-time-business-monitoring-with-klaxon-668fa14c5e38?source=rss-afe0ab1a92ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/668fa14c5e38</guid>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[alerting]]></category>
            <category><![CDATA[business-metrics]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[data-platforms]]></category>
            <dc:creator><![CDATA[Niranjan Kumar]]></dc:creator>
            <pubDate>Thu, 29 May 2025 06:03:52 GMT</pubDate>
            <atom:updated>2025-05-29T06:03:52.034Z</atom:updated>
            <content:encoded><![CDATA[<p>Co-authored with <a href="https://medium.com/u/1fa45a4d386b">Sundaram Dubey</a></p><p>Imagine it’s a Friday night, the peak of demand in cities across the country. Kitchens across the city are buzzing, orders are skyrocketing, and delivery partners are navigating through bustling streets to ensure timely deliveries. Amidst this orchestrated chaos, our system acts as the vigilant eyes and ears of Swiggy, constantly scanning for any anomalies or disruptions in the order-to-delivery process. For instance, if there’s an unexpected surge in orders from a particular area, or if a key restaurant partner suddenly goes offline, our system instantly flags these issues. This isn’t just about detecting problems; it’s about enabling immediate action.</p><p>At Swiggy, we understand that the key to maintaining its edge lies in the power of real-time insights and proactive problem-solving. This is where the pivotal role of Klaxon, in-house business monitoring and alerting system comes into play. It allows users to set up custom alerts based on their specific business needs, helping them stay on top of critical metrics and take action in real-time. Klaxon has seen significant adoption across the organization, with over 300+ alerts currently live on the platform. On a regular day, Klaxon sends out more than 1.5 million alerts, playing a critical role in keeping teams informed of important metrics and potential issues in real-time.</p><p>Let’s dive into how Klaxon has evolved to become the backbone of Swiggy’s alerting ecosystem.</p><h3>Vision:</h3><p>Our vision is to embrace a customer-backward approach, providing businesses with a powerful and flexible platform that enables them to seamlessly monitor and analyze critical metrics. By centering on their customers’ needs, businesses can make informed decisions and take timely actions to enhance operations and deliver exceptional value to their customers.</p><h3>Mission:</h3><p>To enable the Org to identify meaningful incidents</p><ul><li><strong>Actionable</strong>: The incident requires action to prevent some level of business impact.</li><li><strong>Comprehensive</strong>: You have all causal and symptomatic alerts that stem from the root cause.</li><li><strong>Contextualised</strong>: Information to diagnose and remediate the incident is provided across teams and topologies, including diagnostic indicators and documentation.</li></ul><h3>Introducing Klaxon Alerting Platform</h3><p>Klaxon is an alerting system designed to monitor real-time events across Swiggy’s operations. It helps track key business activities like customer orders, operational changes, and vendor partner serviceability. Built around complex event processing (CEP), Klaxon analyzes data from multiple sources to detect patterns that require immediate action. Whether it’s a spike in customer grievances or a dip in order completion rates, Klaxon enables teams to quickly respond to emerging issues and maintain smooth operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-TEkZSMgXPls4QwWTPT9tQ.png" /><figcaption>Klaxon Architecture</figcaption></figure><p>The Klaxon alerting system is designed to automate the creation and delivery of alerts based on specific business events. Here’s an overview of how the system works:</p><ol><li><strong>User Interaction: </strong>The process begins when a Klaxon user defines a trigger condition and creates an alert based on predefined timeout events or real-time events.</li><li><strong>Klaxon Service: </strong>When an event occurs, the Klaxon Service captures the event details and pushes the data to a Kafka event stream. The system integrates with various data sources like Hive/Snowflake to schedule and trigger data-driven alerts. The alert template, once created and recipients added, is scheduled for execution.</li><li><strong>Real-Time Streaming Job: </strong>A real-time streaming job listens for these event triggers, converts them into actionable alerts, and then publishes the event data to the <em>swiss_armstrong</em> Kafka topic.</li><li><strong>Event Processing: </strong>The <em>swiss_armstrong </em>Kafka topic is consumed by the Armstrong Kafka consumer, which reads the event information and stores it in the Armstrong database. This forms the basis for further alert actions.</li><li><strong>Alert Mediums and Notification Delivery: </strong>Based on the user preferences and configurations, alerts are delivered via multiple mediums such as: SMS (Leveraging internal SMS APIs like Decom and Narad), Email (Using AWS SES to send email notifications) and Slack (Messaging via the Slack SDK for internal team communication).</li><li><strong>Response and Metrics:</strong> The system captures responses from the recipients and tracks metrics on alert performance to measure its effectiveness and allow further optimization.</li><li><strong>Technologies Used: </strong>Apache Kafka, Apache Flink (Internally called as Rill), Databricks, Snowflake, Hive, AWS SES, Slack SDK, and SMS APIs.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sHtTV2wfrUM3xRF6.png" /><figcaption>Klaxon Platform</figcaption></figure><h3>Key Capabilities of Klaxon:</h3><h3>UX Capabilities:</h3><ol><li><strong>Multi-Channel Alert Delivery</strong>: Klaxon supports a variety of alerting channels including email (for all internal users), Slack (DMs and channels for collaborative visibility), SMS (targeting external stakeholders like DEs and restaurant partners), push notifications (real-time updates for DEs via the app), and automatic FreshDesk ticket creation (for Customer Care agents to take swift action).</li><li><strong>Flexible Alert Types &amp; Personalization</strong>: Offers both real-time alerts (via Kafka) and batched alerts (via Hive/Snowflake). Users can personalize alert content with dynamic elements like names and metric values to ensure messages are relevant and engaging.</li><li><strong>End-to-End Testing Capabilities</strong>: Users can test alerts thoroughly — both real-time and batched — before going live. This helps catch issues early, reduces platform team debugging efforts, and ensures smoother launches.</li><li><strong>Improved Visibility &amp; Performance Tracking</strong>: Each alert comes with a performance dashboard showing key metrics like success and open rates. Users can view logic, edit, or clone alerts instantly to adapt to changing needs.</li><li><strong>Dedicated User Profile &amp; Engagement Insights</strong>: A new profile section gives users a consolidated view of all their alerts. Email alerts now support acknowledgement tracking, providing open and click-through rates to measure effectiveness.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qg-O5Ne0ksQB7wE2.png" /><figcaption>Alert creation steps</figcaption></figure><h3>Technical Improvements</h3><ol><li><strong>Simplified Operations:</strong> We’ve made Klaxon more efficient by reducing the complexity of our deployment infrastructure. By deprecating two redundant deployment units (Swiss-klaxon-ui and swiss-klaxon-preprod-ui), we’ve streamlined operations, leading to faster development cycles and a more maintainable platform.</li><li><strong>Enhanced UI Efficiency:</strong> Our user interface is now optimized, using fewer resources while delivering the same robust functionality. This improvement not only reduces bandwidth requirements but also ensures a smoother experience for developers and users alike.</li><li><strong>Lowered On-Call Dependencies: </strong>We’ve significantly reduced the need for on-call interventions, particularly when it comes to managing dynamic notification groups. Updates to group creation are now automated, minimizing manual work and bug fixes, particularly those carried over from Klaxon V1.</li></ol><h3>Cost Optimization</h3><ol><li><strong>Streamlined Real-Time Alerts: </strong>We’ve consolidated our alerting mechanisms, cutting down on operational costs by 50–60%. By reducing the number of Kafka jobs from 30 to 8, we’ve made alert management more efficient without compromising performance.</li><li><strong>More Cost-Effective Batch Alerts: </strong>We’ve optimized batch alert costs by transitioning to a leaner, single-node setup for Databricks with an on-demand instance. This change alone has cut Databricks unit costs for new batch alerts by 50%, bringing significant savings.</li></ol><h3>Klaxon usage, adoption and Impact:</h3><p>Klaxon has seen strong adoption across the organization, with a growing number of active alerts being managed on the platform. On a daily basis, Klaxon sends a substantial volume of alerts, playing a vital role in ensuring teams stay updated on key metrics and potential issues in real time. This widespread usage showcases Klaxon’s effectiveness as a reliable, scalable alerting system, supporting the complex operational needs of the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4VnwHVDzXSJs5cH7" /><figcaption>Daily Klaxon Alerts</figcaption></figure><p><strong>Impact Stories: How Smart Alerts Are Powering Smarter Decisions</strong></p><p>Klaxon’s intelligent alerting system isn’t just about sending messages — it’s about making the right people act at the right time. Here’s how our alerting capabilities are creating tangible impact across teams, roles, and customer touchpoints:</p><p><strong>For Delivery Executives: Improving On-Ground Execution</strong></p><ul><li><strong>Push Notifications for DEs</strong> — Real-time push alerts, now rolled out nationwide, have reduced damages to fragile items. DEs receive contextual cues during delivery, improving care and accuracy mid-route.</li><li><strong>SMS Alerts for Cake Deliveries</strong> — To address spillage and packaging issues in cake orders, DEs now get SMS alerts just in time. This has notably reduced complaints and improved handling quality.</li></ul><p><strong>For Operations Teams: Enhancing Speed &amp; Reliability</strong></p><ul><li><strong>InstaMart Delay Alerts</strong> — Real-time alerts on delays helped reduce late deliveries and improved fulfillment SLAs. This has directly impacted customer satisfaction and operational throughput.</li><li><strong>Food Order Delay Escalation</strong> — Klaxon flags delays at various stages of the order lifecycle. This allows teams to reassign DEs or take immediate action, boosting on-time deliveries city by city.</li></ul><p><strong>For Customer Support: Responding Proactively</strong></p><ul><li><strong>Poor Ratings on Premium Orders</strong> — When high-value customers rate orders poorly, instant alerts allow CC teams to reach out proactively. This has improved retention and increased orders per customer.</li><li><strong>Social Media Escalation Alerts</strong> — Klaxon monitors chats for social keywords and reroutes them to specialist agents. Result? Fewer escalations, faster response times, and better brand control.</li></ul><p><strong>Looking Ahead: Smarter, Simpler, More Impactful</strong></p><p>As we continue to evolve Klaxon, our focus remains on enhancing usability, performance, and value across the board. We’re working towards simplifying the backend architecture by unifying environments for greater efficiency and ease of maintenance. Additionally, we plan to introduce lightweight mechanisms to surface the impact of alerts, helping teams better understand their effectiveness. To further optimize alert relevance, we also aim to flag low-utility alerts, allowing teams to fine-tune their focus where it truly matters.</p><p><strong>Acknowledgements:</strong></p><p>Shout out to the Klaxon team: <a href="/service/mailto:sundaram.dubey@swiggy.in">Sundaram Dubey</a>, <a href="/service/mailto:ishita.dutta@swiggy.in">Ishita Dutta</a>, <a href="/service/mailto:sakshi.rai1_int@external.swiggy.in">Sakshi Rai</a>, <a href="/service/mailto:ravi.kumar12@swiggy.in">Ravi Kumar</a> and <a href="/service/mailto:vikash.s@swiggy.in">Vikash Singh</a> for their hard work in making Klaxon a reality!</p><p>Special thanks to <a href="/service/mailto:jairaj.s@swiggy.in">Jairaj Sathyanarayana</a>, <a href="/service/mailto:goda.doreswamy@swiggy.in">Goda Doreswamy Ramkumar</a> and <a href="/service/mailto:amaresh.marripudi@swiggy.in">Amaresh Marripudi</a> for their unwavering support throughout the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=668fa14c5e38" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swiggy-bytes/enabling-real-time-business-monitoring-with-klaxon-668fa14c5e38">Enabling Real-Time Business Monitoring with Klaxon</a> was originally published in <a href="https://medium.com/swiggy-bytes">Swiggy Bytes — Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enabling Real-Time Business Monitoring with Klaxon]]></title>
            <link>https://medium.com/@niks4one/enabling-real-time-business-monitoring-with-klaxon-dc72076f01d2?source=rss-afe0ab1a92ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc72076f01d2</guid>
            <category><![CDATA[monitoring-software]]></category>
            <category><![CDATA[metrics-and-analytics]]></category>
            <category><![CDATA[alerting]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[data-platforms]]></category>
            <dc:creator><![CDATA[Niranjan Kumar]]></dc:creator>
            <pubDate>Wed, 28 May 2025 10:47:10 GMT</pubDate>
            <atom:updated>2025-05-29T05:48:05.775Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine it’s a Friday night, the peak of demand in cities across the country. Kitchens across the city are buzzing, orders are skyrocketing, and delivery partners are navigating through bustling streets to ensure timely deliveries. Amidst this orchestrated chaos, our system acts as the vigilant eyes and ears of Swiggy, constantly scanning for any anomalies or disruptions in the order-to-delivery process. For instance, if there’s an unexpected surge in orders from a particular area, or if a key restaurant partner suddenly goes offline, our system instantly flags these issues. This isn’t just about detecting problems; it’s about enabling immediate action.</p><p>At Swiggy, we understand that the key to maintaining its edge lies in the power of real-time insights and proactive problem-solving. This is where the pivotal role of Klaxon, in-house business monitoring and alerting system comes into play. It allows users to set up custom alerts based on their specific business needs, helping them stay on top of critical metrics and take action in real-time. Klaxon has seen significant adoption across the organization, with over 300+ alerts currently live on the platform. On a regular day, Klaxon sends out more than 1.5 million alerts, playing a critical role in keeping teams informed of important metrics and potential issues in real-time.</p><p>Let’s dive into how Klaxon has evolved to become the backbone of Swiggy’s alerting ecosystem.</p><h3>Vision:</h3><p>Our vision is to embrace a customer-backward approach, providing businesses with a powerful and flexible platform that enables them to seamlessly monitor and analyze critical metrics. By centering on their customers’ needs, businesses can make informed decisions and take timely actions to enhance operations and deliver exceptional value to their customers.</p><h3>Mission:</h3><p>To enable the Org to identify meaningful incidents</p><ul><li><strong>Actionable</strong>: The incident requires action to prevent some level of business impact.</li><li><strong>Comprehensive</strong>: You have all causal and symptomatic alerts that stem from the root cause.</li><li><strong>Contextualised</strong>: Information to diagnose and remediate the incident is provided across teams and topologies, including diagnostic indicators and documentation.</li></ul><h3>Introducing Klaxon Alerting Platform</h3><p>Klaxon is an alerting system designed to monitor real-time events across Swiggy’s operations. It helps track key business activities like customer orders, operational changes, and vendor partner serviceability. Built around complex event processing (CEP), Klaxon analyzes data from multiple sources to detect patterns that require immediate action. Whether it’s a spike in customer grievances or a dip in order completion rates, Klaxon enables teams to quickly respond to emerging issues and maintain smooth operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-TEkZSMgXPls4QwWTPT9tQ.png" /><figcaption>Klaxon Architecture</figcaption></figure><p>The Klaxon alerting system is designed to automate the creation and delivery of alerts based on specific business events. Here’s an overview of how the system works:</p><ol><li><strong>User Interaction: </strong>The process begins when a Klaxon user defines a trigger condition and creates an alert based on predefined timeout events or real-time events.</li><li><strong>Klaxon Service: </strong>When an event occurs, the Klaxon Service captures the event details and pushes the data to a Kafka event stream. The system integrates with various data sources like Hive/Snowflake to schedule and trigger data-driven alerts. The alert template, once created and recipients added, is scheduled for execution.</li><li><strong>Real-Time Streaming Job: </strong>A real-time streaming job listens for these event triggers, converts them into actionable alerts, and then publishes the event data to the <em>swiss_armstrong</em> Kafka topic.</li><li><strong>Event Processing: </strong>The <em>swiss_armstrong </em>Kafka topic is consumed by the Armstrong Kafka consumer, which reads the event information and stores it in the Armstrong database. This forms the basis for further alert actions.</li><li><strong>Alert Mediums and Notification Delivery: </strong>Based on the user preferences and configurations, alerts are delivered via multiple mediums such as: SMS (Leveraging internal SMS APIs like Decom and Narad), Email (Using AWS SES to send email notifications) and Slack (Messaging via the Slack SDK for internal team communication).</li><li><strong>Response and Metrics:</strong> The system captures responses from the recipients and tracks metrics on alert performance to measure its effectiveness and allow further optimization.</li><li><strong>Technologies Used: </strong>Apache Kafka, Apache Flink (Internally called as Rill), Databricks, Snowflake, Hive, AWS SES, Slack SDK, and SMS APIs.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hiMoErz4APr54ypYNzQGA.png" /><figcaption>Klaxon Platform</figcaption></figure><h3>Key Capabilities of Klaxon:</h3><h3>UX Capabilities:</h3><ol><li><strong>Multi-Channel Alert Delivery</strong>: Klaxon supports a variety of alerting channels including email (for all internal users), Slack (DMs and channels for collaborative visibility), SMS (targeting external stakeholders like DEs and restaurant partners), push notifications (real-time updates for DEs via the app), and automatic FreshDesk ticket creation (for Customer Care agents to take swift action).</li><li><strong>Flexible Alert Types &amp; Personalization</strong>: Offers both real-time alerts (via Kafka) and batched alerts (via Hive/Snowflake). Users can personalize alert content with dynamic elements like names and metric values to ensure messages are relevant and engaging.</li><li><strong>End-to-End Testing Capabilities</strong>: Users can test alerts thoroughly — both real-time and batched — before going live. This helps catch issues early, reduces platform team debugging efforts, and ensures smoother launches.</li><li><strong>Improved Visibility &amp; Performance Tracking</strong>: Each alert comes with a performance dashboard showing key metrics like success and open rates. Users can view logic, edit, or clone alerts instantly to adapt to changing needs.</li><li><strong>Dedicated User Profile &amp; Engagement Insights</strong>: A new profile section gives users a consolidated view of all their alerts. Email alerts now support acknowledgement tracking, providing open and click-through rates to measure effectiveness.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VM5-yRlrdXJmh6UGx8YYlA.png" /><figcaption>Alert creation steps</figcaption></figure><h3>Technical Improvements</h3><ol><li><strong>Simplified Operations:</strong> We’ve made Klaxon more efficient by reducing the complexity of our deployment infrastructure. By deprecating two redundant deployment units (Swiss-klaxon-ui and swiss-klaxon-preprod-ui), we’ve streamlined operations, leading to faster development cycles and a more maintainable platform.</li><li><strong>Enhanced UI Efficiency:</strong> Our user interface is now optimized, using fewer resources while delivering the same robust functionality. This improvement not only reduces bandwidth requirements but also ensures a smoother experience for developers and users alike.</li><li><strong>Lowered On-Call Dependencies: </strong>We’ve significantly reduced the need for on-call interventions, particularly when it comes to managing dynamic notification groups. Updates to group creation are now automated, minimizing manual work and bug fixes, particularly those carried over from Klaxon V1.</li></ol><h3>Cost Optimization</h3><ol><li><strong>Streamlined Real-Time Alerts: </strong>We’ve consolidated our alerting mechanisms, cutting down on operational costs by 50–60%. By reducing the number of Kafka jobs from 30 to 8, we’ve made alert management more efficient without compromising performance.</li><li><strong>More Cost-Effective Batch Alerts: </strong>We’ve optimized batch alert costs by transitioning to a leaner, single-node setup for Databricks with an on-demand instance. This change alone has cut Databricks unit costs for new batch alerts by 50%, bringing significant savings.</li></ol><h3>Klaxon usage, adoption and Impact:</h3><p>Klaxon has seen strong adoption across the organization, with a growing number of active alerts being managed on the platform. On a daily basis, Klaxon sends a substantial volume of alerts, playing a vital role in ensuring teams stay updated on key metrics and potential issues in real time. This widespread usage showcases Klaxon’s effectiveness as a reliable, scalable alerting system, supporting the complex operational needs of the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f5EKd3syyLxKhYU2" /><figcaption>Daily Klaxon Alerts</figcaption></figure><p><strong>Impact Stories: How Smart Alerts Are Powering Smarter Decisions</strong></p><p>Klaxon’s intelligent alerting system isn’t just about sending messages — it’s about making the right people act at the right time. Here’s how our alerting capabilities are creating tangible impact across teams, roles, and customer touchpoints:</p><p><strong>For Delivery Executives: Improving On-Ground Execution</strong></p><ul><li><strong>Push Notifications for DEs</strong> — Real-time push alerts, now rolled out nationwide, have reduced damages to fragile items. DEs receive contextual cues during delivery, improving care and accuracy mid-route.</li><li><strong>SMS Alerts for Cake Deliveries</strong> — To address spillage and packaging issues in cake orders, DEs now get SMS alerts just in time. This has notably reduced complaints and improved handling quality.</li></ul><p><strong>For Operations Teams: Enhancing Speed &amp; Reliability</strong></p><ul><li><strong>InstaMart Delay Alerts</strong> — Real-time alerts on delays helped reduce late deliveries and improved fulfillment SLAs. This has directly impacted customer satisfaction and operational throughput.</li><li><strong>Food Order Delay Escalation</strong> — Klaxon flags delays at various stages of the order lifecycle. This allows teams to reassign DEs or take immediate action, boosting on-time deliveries city by city.</li></ul><p><strong>For Customer Support: Responding Proactively</strong></p><ul><li><strong>Poor Ratings on Premium Orders</strong> — When high-value customers rate orders poorly, instant alerts allow CC teams to reach out proactively. This has improved retention and increased orders per customer.</li><li><strong>Social Media Escalation Alerts</strong> — Klaxon monitors chats for social keywords and reroutes them to specialist agents. Result? Fewer escalations, faster response times, and better brand control.</li></ul><p><strong>Looking Ahead: Smarter, Simpler, More Impactful</strong></p><p>As we continue to evolve Klaxon, our focus remains on enhancing usability, performance, and value across the board. We’re working towards simplifying the backend architecture by unifying environments for greater efficiency and ease of maintenance. Additionally, we plan to introduce lightweight mechanisms to surface the impact of alerts, helping teams better understand their effectiveness. To further optimize alert relevance, we also aim to flag low-utility alerts, allowing teams to fine-tune their focus where it truly matters.</p><p><strong>Acknowledgements:</strong></p><p>Shout out to the Klaxon team: <a href="/service/mailto:sundaram.dubey@swiggy.in">Sundaram Dubey</a>, <a href="/service/mailto:ishita.dutta@swiggy.in">Ishita Dutta</a>, <a href="/service/mailto:sakshi.rai1_int@external.swiggy.in">Sakshi Rai</a>, <a href="/service/mailto:ravi.kumar12@swiggy.in">Ravi Kumar12</a> and <a href="/service/mailto:vikash.s@swiggy.in">Vikash Singh</a> for their hard work in making Klaxon a reality!</p><p>Special thanks to <a href="/service/mailto:jairaj.s@swiggy.in">Jairaj Sathyanarayana</a>, <a href="/service/mailto:goda.doreswamy@swiggy.in">Goda Doreswamy Ramkumar</a> and <a href="/service/mailto:amaresh.marripudi@swiggy.in">Amaresh Marripudi</a> for their unwavering support throughout the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc72076f01d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>