<?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 Pratyush Shukla on Medium]]></title>
        <description><![CDATA[Stories by Pratyush Shukla on Medium]]></description>
        <link>https://medium.com/@pratyush.shukla075?source=rss-17c426127e8e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*45JINZT7W8z4e70kQylgdw.jpeg</url>
            <title>Stories by Pratyush Shukla on Medium</title>
            <link>https://medium.com/@pratyush.shukla075?source=rss-17c426127e8e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:35:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pratyush.shukla075/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[Navigating Complex Product Launches]]></title>
            <link>https://medium.com/walmartglobaltech/navigating-complex-product-launches-02e81b278413?source=rss-17c426127e8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/02e81b278413</guid>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[application]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Pratyush Shukla]]></dc:creator>
            <pubDate>Wed, 19 Mar 2025 12:40:46 GMT</pubDate>
            <atom:updated>2025-03-19T12:40:46.485Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Introduction</strong></h3><p>In the intricate world of product development, particularly when multiple teams are involved, the margin for error is slim. Product launches are always a high-stakes endeavor, but when they involve multiple teams, systems, and stakeholders, the complexity increases exponentially. In such an environment, even minor issues can lead to significant delays, cost overruns, and dissatisfied customers.</p><p>The key to overcoming these challenges lies in being proactive rather than reactive.</p><p>The success of such a venture depends on the ability to anticipate, prepare, and respond effectively to potential challenges. Our recent experience at Walmart, during a high-stakes product launch, underscores the pressing need for sophisticated, proactive systems and tools.</p><h3><strong>Vision</strong></h3><p><strong>Our vision was simple yet powerful</strong>: we wanted to create a platform that could not only detect issues in real-time but also provide a complete, end-to-end view of the product lifecycle. This platform needed to be flexible enough to handle the inevitable fluctuations in business requirements and scalable enough to support a wide range of services. Most importantly, it had to facilitate quick decision-making and empower teams to resolve problems before they escalated.</p><p>With this vision in mind, we set out to build three key tools: a Monitoring System, an Analyzer Tool, and a War Room Scenario Mapping framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*X8-A5jKdt_cj7sN5XyIFzQ.png" /></figure><h3><strong>Solution</strong></h3><p><strong>Monitoring System<br></strong>Managing a complex project requires clear visibility into every step of the process. The first tool we developed was a Monitoring System that tracks orders as they move through key stages — order creation, packing, dispatching, and delivery. We identified critical phases where bottlenecks were most likely to occur, which allowed us to focus our attention on the areas that would have the biggest impact.</p><ol><li><strong>Critical Phase Identification:</strong> Identify and define critical stages in the order process such as order creation, packing, dispatching etc</li><li><strong>Alert System:</strong> Sends timely notifications to the support and dev teams when an order fails to pass a critical stage within the expected period.</li><li><strong>Data Analysis and Improvement:</strong> Use the data captured from the order tracking system to identify common bottlenecks and issues leading to delays.</li></ol><p><strong>Impact</strong>: The monitoring system’s real-time alerts allowed us to catch delays that would have otherwise gone unnoticed until it was too late, significantly reducing delays and improving overall customer satisfaction along with reducing the blast radius.</p><p><strong>Analyzer Tool<br></strong>While monitoring is crucial, effective troubleshooting is what turns information into action. This is where our Analyzer Tool comes into play. Designed to provide deep insights into the status of an order, the Analyzer Tool acts as a central hub for all order-related data, offering a holistic view across systems and teams.</p><ol><li><strong>Improved troubleshooting</strong>: Easily track and analyze the current state of an order, which can significantly improve troubleshooting efforts. This can lead to faster problem resolution.</li><li><strong>Scalability and adaptability</strong>: The ability to add or remove services provides scalability and adaptability to changing business needs</li><li><strong>Comprehensive view:</strong> Acting as a gateway to different systems, the solution offers a comprehensive view of the order.</li></ol><p><strong>Impact</strong>: By providing real-time, comprehensive insights into order states, the Analyzer Tool reduced the time spent diagnosing issues, helping us quickly resolve potential problems before they impacted the launch.</p><p><strong>War Room Scenario Mapping<br></strong>In complex launches, issues are inevitable. The challenge is to minimize the damage when they occur. One of the most valuable strategies we implemented was a War Room Scenario Mapping exercise. This proactive approach involved anticipating potential roadblocks and creating predefined response plans for each scenario.</p><ol><li><strong>Strategic Pre-emptive Planning</strong>: Prior to the launch, we conducted exhaustive scenario mapping to identify high-risk areas. We developed a comprehensive suite of war room scenarios, complete with predefined resolution strategies. This level of planning allowed teams to tackle issues swiftly, with clear instructions on how to address them.</li><li><strong>API Library for Debugging</strong>: To support this effort, we built an extensive library of APIs that allowed for quick debugging and issue resolution. These APIs were readily available to all teams, reducing friction during high-pressure situations.</li><li><strong>Role of the Analyser Tool</strong>: During these war room scenarios, the Analyser Tool played a pivotal role, offering critical insights into ongoing issues. Its comprehensive view of the system allowed us to make data-driven decisions and react more effectively to problems.</li></ol><p><strong>Impact</strong>: The combination of scenario mapping, API debugging, and the Analyser Tool drastically improved our response times, allowing us to pre-emptively address issues that could have escalated into larger problems.</p><h3><strong>Conclusion</strong></h3><p>Launching a complex product, especially one involving multiple teams and systems, requires more than just technical knowledge — it demands strategic foresight, rigorous planning, and proactive tools. Through our experience at Walmart, we learned that the key to a successful launch is reducing the time it takes to detect, troubleshoot, and resolve issues. The Monitoring System, Analyser Tool, and War Room Scenario Mapping framework helped us achieve just that.</p><h3><strong>Key Takeaways</strong></h3><p>For those managing similarly complex projects, the lessons we have learned are clear:</p><ol><li>Invest in monitoring systems that can detect issues early.</li><li>Develop adaptable tools that offer a comprehensive, real-time view of your process.</li><li>Pre-emptively map out potential issues and create resolution plans ahead of time.</li></ol><p>By adopting these strategies, you can navigate the complexities of multi-team product launches with greater confidence and success. These tools are not just nice to have they are essential to reducing downtime, minimizing errors, and ensuring a smooth launch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02e81b278413" width="1" height="1" alt=""><hr><p><a href="https://medium.com/walmartglobaltech/navigating-complex-product-launches-02e81b278413">Navigating Complex Product Launches</a> was originally published in <a href="https://medium.com/walmartglobaltech">Walmart Global 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[Effortlessly Debugging Docker Images with IntelliJ and Docker]]></title>
            <link>https://medium.com/walmartglobaltech/effortlessly-debugging-docker-images-with-intellij-and-docker-269f91b2162c?source=rss-17c426127e8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/269f91b2162c</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[intellij]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[cicd]]></category>
            <dc:creator><![CDATA[Pratyush Shukla]]></dc:creator>
            <pubDate>Wed, 18 Oct 2023 05:26:58 GMT</pubDate>
            <atom:updated>2023-10-18T05:26:58.133Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Need:</strong></p><p>Most developers work in multiple deployment environments, including production, development, and testing. Any delay or bugs in these servers can impact all the development deployments. A widespread practice among developers is to run the code on their local machines in IntelliJ or other IDEs. However, the code sometimes behaves differently when running in IntelliJ than when running on a Docker container.</p><p><strong>Docker</strong>:</p><p>Docker is a powerful tool that allows developers to build, test, and deploy applications quickly. Additionally, using Docker, we can generate an image and push it from lower environments up to PROD, thus maintaining consistency and reducing the scope of introducing bugs in higher environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ItjTVCY7KFx0seeOD4Dtqw.png" /></figure><p><em>Image source: </em><a href="https://en.m.wikipedia.org/wiki/File:Docker_%28container_engine%29_logo.svg"><em>https://en.m.wikipedia.org/wiki</em></a></p><p><strong>Use-case:</strong></p><p>In some cases, the code was passing in IntelliJ, but once the same code was pushed to DEV, startup of the Spring Boot application failed. The main reason was that our code was reading certs from our class path. The way the class path was getting picked in IntelliJ was different from the way our Docker container was searching for it. This was easily identified once we ran the published Docker image in our local Docker desktop and connected and debugged the same using IntelliJ.</p><p><strong>Other important use-cases which can be targeted via this would be:</strong></p><p>1. Early identification and fixation of errors instead of catching it later during the deployment phase.</p><p>2. Testing and validation of changes in a near production like environment.</p><p>3. Debugging images in local can help identify and resolve connectivity issues, resource allocation issues or other problems that may affect the startup and functionality of the application.</p><p><strong>Tools Used:</strong></p><ol><li>Docker Desktop</li><li>IntelliJ</li></ol><p><strong>Approach:</strong></p><p>1. Run the image on local docker using the command:</p><pre>docker run -it -p 8080:8080 -e &quot;JAVA_TOOL_OPTIONS=\&quot; agentlib:jdwp=transport=dt_socket,address=8080,server=y,suspend=n\&quot;&quot; &lt;IMAGE_NAME&gt;</pre><p>2. In IntelliJ, follow these steps:</p><p>- Select Edit Configurations</p><p>- Add new configuration “Remote JVM Debug”</p><p>- Set the port as 8080</p><p>- Debug the image and the same will be connected to the running docker image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F5Z5UuWHGY3YaO9M6eBgOA.png" /></figure><p><strong>Conclusion</strong>:</p><p>Debugging Docker images is an essential skill for developers, and by following the approach discussed in this article, we can easily identify and fix issues that arise during deployment. The power of docker can easily allow developers to skilfully navigate through the complexities of their applications. Are you ready to hop on the journey of unlocking the potential of Docker and become a great problem solver?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=269f91b2162c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/walmartglobaltech/effortlessly-debugging-docker-images-with-intellij-and-docker-269f91b2162c">Effortlessly Debugging Docker Images with IntelliJ and Docker</a> was originally published in <a href="https://medium.com/walmartglobaltech">Walmart Global 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[KAFKA Automation using KARATE]]></title>
            <link>https://medium.com/walmartglobaltech/kafka-automation-using-karate-6a129cfdc210?source=rss-17c426127e8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a129cfdc210</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[karate]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[cicd]]></category>
            <dc:creator><![CDATA[Pratyush Shukla]]></dc:creator>
            <pubDate>Thu, 15 Apr 2021 19:24:24 GMT</pubDate>
            <atom:updated>2021-04-15T19:24:24.007Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Need for automation:</strong></p><p>In continuous integration (CI), development teams implement small changes and check in code to version control repositories frequently. Continuous delivery (CD) automates deployment to selected infrastructure environments. Most developers work on multiple deployment environment like production, development and testing. Any delay or bugs on these servers impacts all the development deployments.</p><p>Automation reduces the number of errors that can take place in the many repetitive steps of CI and CD.</p><p>An added advantage is that it saves developers time to be spent on product development and also reduces the risk of shipping erroneous code to production.</p><p><strong>Karate:</strong></p><p>Karate is a powerful automation tool by Intuit and is based on the BDD syntax popularised by Cucumber thus making it language neutral and easy for even non-programmers. Test execution and report generation feels like any standard Java project. You don’t have to compile code. Just write tests in a simple, readable syntax.</p><p><strong>Use case :</strong></p><p>Our service hosted on Azure private PaaS is using Cucumber framework for doing the end to end functional tests of our REST APIs. Since we were already accustomed to Cucumber and had the tests written, we planned to explore the possibility of using Karate for handling the automation for our newly introduced Kafka component. And luckily, the decision turned out to be good one. :D</p><p>The major issues which we faced while running our existing Auto was the fact that we had to maintain a separate validation service using JPA to connect to our database and carry out the operations. With most of the teams working remotely, an unnecessary number of DB connections were being established thus blocking the developers and hindering their productivity. Even resource optimisation was not in place since a lot of resources were used even when no runs were happening.</p><p>However, since Karate provides an out of the box support to connect to various DB’s/Azure Resources/Kafka (SQL, blob, cosmos, etc) via feature files to run Java Classes inside feature files and rigorous methods to perform validations, we could do away with the validation service and move al the code to Karate.</p><p>Exploring the various advantages with each step, let’s take a look at how we implemented Kafka automation using karate.</p><p><strong>Setup :</strong></p><p>The scenario mainly consists of two services (Service A and Service B) interacting with each other using Kafka.</p><p>Flow would be as follows :</p><ul><li>Service A produces messages.</li><li>Service B consumes the messages and produces an Acknowledgment packet based on the consumption of messages.</li><li>On successful consumption, Service B produces a Business Packet as well.</li></ul><p>Flow which will be simulated and automated using Karate:</p><ul><li>Message Production from Service A to Service B.</li><li>Acknowledgement Packet validation from Service B to Service A.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*_pB7ynyZJ_SHgmFI.png" /><figcaption>Flow Simulated for our use case</figcaption></figure><p><strong>Scenario Covered</strong></p><p>In the below table, each packet produced by the Producer can be uniquely identified using the ID field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVVThLcFok0MOYSDQH3PkA.png" /><figcaption>Scenario Covered</figcaption></figure><p>Create a Producer for populating messages to the topic for various scenarios ( successful as well as erroneous Packets )</p><ul><li>Create a singleton class for updating a HashMap which would contain the entries in the form of &lt; KEY , TEST-CASE &gt; . This would be called every time a new message is published by the producer.<br>KEY → field through which we can uniquely identify the PRODUCER — CONSUMER pair (ID in our case).<br>VALUE → name of the feature file which should be executed for that particular scenario.</li><li>Create another Auto Consumer with a unique group id and listening to outgoing topics.</li><li>Loop over all the messages picked by the Consumer and based on the ID, read the HashMap to determine the test case (feature file) to be executed.</li></ul><p>The scenario defined in Table above would be handled in the following way by this approach :</p><p>ID1 -&gt; Generated by Auto Producer → Entry will be there in HashMap →<br>&lt; ID1 , FeatureFile1.feature &gt;<br>ID2 -&gt; Generated by Auto Producer → Entry will be there in HashMap →<br>&lt; ID2 , FeatureFile2.feature &gt;<br>ID3 -&gt; Generated by Auto Producer → Entry will be there in HashMap →<br>&lt; ID3 , FeatureFile3.feature &gt;</p><p>Once all the messages are published our Auto Consumer will kick in.</p><p>ID1 → Read from HashMap based on ID1 → Determine the feature file for that case ( FeatureFile1.feature ) and execute the set of validations.<br>ID2 → Read from HashMap based on ID2 → Determine the feature file for that case ( FeatureFile2.feature ) and execute the set of validations.<br>ID3 → Read from HashMap based on ID3 → Determine the feature file for that case ( FeatureFile3.feature ) and execute the set of validations.</p><p><strong>Maven dependencies used :</strong></p><p>Karate Dependency</p><pre>&lt;dependency&gt;<br>   &lt;groupId&gt;com.intuit.karate&lt;/groupId&gt;<br>   &lt;artifactId&gt;karate-apache&lt;/artifactId&gt;<br>   &lt;version&gt; 0.9.5&lt;/version&gt;<br>&lt;/dependency&gt;</pre><p>Kafka Client dependency:</p><pre>&lt;dependency&gt;<br>    &lt;groupId&gt;org.apache.kafka&lt;/groupId&gt;<br>    &lt;artifactId&gt;kafka-clients&lt;/artifactId&gt;<br>    &lt;version&gt;2.5.0&lt;/version&gt;<br>&lt;/dependency&gt;</pre><p><strong>Approach used:</strong></p><p>This is how our Karate feature file will look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*oo0qJVAd-TZTKBqP.png" /><figcaption>Karate feature file used</figcaption></figure><p><strong>Step 1 :</strong></p><p>Reset the offsets used for consumer groups used in your automation scenarios to the latest values so that the messages published for Automation Scenarios would be picked instead of other messages thus ensuring smooth runs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*FzA28M6a_nz4TsPM.png" /><figcaption>Reset offset to latest</figcaption></figure><p>In our feature file, we will be calling the JAVA code to reset the offset to latest before the execution of other steps kicks in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DyzNz-ISpZDwt6kl.png" /><figcaption>Java code used for resetting the offset</figcaption></figure><p><strong>Step 2:</strong></p><p>Produce messages from Service A to Service B.</p><p>In this step, we would be reading the JSON or XML or any other format based on our needs and publish the same to Service B’s incoming topic. Producer is written in JAVA and is a Kafka client that publishes records to the Kafka cluster.</p><p>Karate feature file to publish messages:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*oTPs9BfQkXqgWi4F.png" /><figcaption>Feature file to publish messages</figcaption></figure><p>Java code for sending the data to the subscribed topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mnXMEl3Jxl-OwLy9.png" /><figcaption>Java code for producing messages</figcaption></figure><p><strong>Step 3:</strong></p><p>Validate Acknowledgement packet from Service B to Service A</p><p>Major steps in this scenario will be :</p><ul><li>Fetch acknowledgement packets from Service B to Service A.<br>We will be using a Kafka Client consumer to read messages. Until you call poll(), the consumer is just idling. Only after poll() is invoked, it will initiate a connection to the cluster, get assigned partitions and attempt to fetch messages. So we will call poll() and then wait for some time until the partition is assigned. Then raise a signal ( countdown latch ) so that the constructor can return.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*mX2h4-XGJCSf3i88.png" /><figcaption>Fetch acknowledgement based on ID</figcaption></figure><p>Determine test case to be executed based on ID with which we had published the messages in Step 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*KBPgfAHcJtwzlO3x.png" /><figcaption>Determine test case to be executed</figcaption></figure><p>Perform the set of validations.</p><p><strong>Conclusion:</strong></p><p>After analysing and moving the existing set of tests running on Cucumber to Karate, we definitely saw an improvement in the time taken for test runs because of the parallel runs provided by Karate along with added advantages as :</p><ul><li>Data-driven tests that can even use JSON or CSV sources</li><li>Easy re-use of JSON or JS / Java logic across tests</li><li>Powerful and flexible payload assertions</li><li>Parallel Execution with Reports Aggregated</li><li>Easy CI integration via cross-platform executable / CLI</li></ul><p><strong>Acknowledgements:</strong></p><p>Thanks to <a href="https://medium.com/u/e8ad3283f426">Mayur Patki</a> for helping on finalising the approach and design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a129cfdc210" width="1" height="1" alt=""><hr><p><a href="https://medium.com/walmartglobaltech/kafka-automation-using-karate-6a129cfdc210">KAFKA Automation using KARATE</a> was originally published in <a href="https://medium.com/walmartglobaltech">Walmart Global Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>