<?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 Vishal Neema on Medium]]></title>
        <description><![CDATA[Stories by Vishal Neema on Medium]]></description>
        <link>https://medium.com/@vishalneema?source=rss-1a8ff00d7744------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UellOYgKavMMz6o5SU_zcA.jpeg</url>
            <title>Stories by Vishal Neema on Medium</title>
            <link>https://medium.com/@vishalneema?source=rss-1a8ff00d7744------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:58:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vishalneema/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[A Journey towards Product Modernization]]></title>
            <link>https://medium.com/@vishalneema/a-journey-towards-product-modernization-5a70c40cce34?source=rss-1a8ff00d7744------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a70c40cce34</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-modernization]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[application-modernization]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Vishal Neema]]></dc:creator>
            <pubDate>Mon, 20 Dec 2021 02:03:56 GMT</pubDate>
            <atom:updated>2021-12-20T02:03:56.040Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*VO8ScGFjATMIM9ysEFZDhg.jpeg" /></figure><p>I often go out to spend quality time with my friends and family. We prefer to go to a fine dining restaurant where we can relax, enjoy delicious food and drinks. When choosing the latter, we prefer to have a glass of wine, the older the better. There is an idiom “Old wine and old friends are the best” and I am sure most of us agree to this. The problem is, unlike wine and friends, the software doesn’t get better with age.</p><p>We all know the moment we drive the new car home, off the dealer, it starts to lose its value. Another good example is smartphones. We all use smartphones and needless to say, to stay up to date with technology and the latest apps, it is essential to upgrade phones every few years. In most cases, software is like a new car, like a new smartphone. It starts to lose its value over time. When I say value, it could be related to performance, maintenance, operating cost, scaling capacity or user-friendliness, etc. Some aging is normal, especially considering how quickly software technologies and development techniques have been advancing in recent years; but it is important to understand that software can also age to a point where it becomes unusable. In such cases, the existing code should be refactored, or in more drastic cases, completely rewritten.</p><p><strong>Product modernization</strong> means recognizing the evolving technology climate and adapting to it. As we know, Cloud computing will play a critical role in modernizing the IT environment. In fact, we have embraced the need for this technology, but this doesn’t mean we should automatically switch from on-site systems. Cloud is a viable and exciting delivery model for many applications, but not every workload or application is best done from the cloud. Modernization doesn’t mean an automatic pivot to the cloud.</p><p>Earlier this year, we took the initiative to modernize our product, <strong>VirtualWisdom</strong>. The goal was to run VirtualWisdom, in a federated environment. Initially, planned to run in a three-node cluster with the database running in a separate node. This is eventually to replace one of our hardware appliances.</p><p>This blog is about my learning through this journey along with the challenges that we faced. I will soon write a separate blog on the technology that we chose along with the architecture.</p><h4><strong>What are the key drivers of modernization?</strong></h4><p>Modern application architecture has been evolving continuously to be loosely coupled components. APIs and microservices form an architecture that supports interoperability and business agility, fostering innovation and driving digital transformation. Below are the key drivers for us at Virtana that necessitate the need for modernization</p><ul><li>Customer success</li><li>Business continuity and growth</li><li>Improve agility and scalability</li><li>Faster deployment</li><li>Lower maintenance cost</li></ul><h4><strong>What are the ways of modernization?</strong></h4><p>As mentioned earlier, there could be several reasons to think about application modernization and likewise, there could be several ways to modernize an application. Below are some of the ways I can think of for application modernization.</p><ul><li>Cloud Migration</li><li>Technology Modernization</li><li>Architecture Modernization (Microservices, APIs, Data-Driven, etc.)</li><li>Infrastructure Modernization</li><li>Enhancing UI for better user experience (UX)</li></ul><p>You can choose the latest and greatest technology available in the market but no matter what you choose, it should align with your business and longtime vision for the product that you plan to modernize. To maintain the business continuity and scale its expansion, it is also critical to continue to support the existing customers who are using your product for years and serve a good customer base</p><p>Among all the options mentioned above, we choose to go with infrastructure &amp; technology modernization where we decided to run each of our Java services into a container so that each of the services can be scaled as the need arises. This would also allow us to have minimum impact on the existing architecture and platform.</p><p>Infrastructure modernization means reducing dependency on the hardware appliances on which the application is running while supporting the same performance and load.</p><h4><strong>Challenges</strong></h4><p>As with every business, there are challenges in planning such types of work. Product management and sales team want engineering team to deliver new features to customers while engineering wants to have better agility and scalability to sustain in future. Furthermore, there must be a good balance between feature development, refactoring and scaling to support application modernization. Fortunately, at Virtana, the leadership team is aligned to have this balance and appreciated the need for modernization effort along with feature development.</p><p>Here are some of the challenges as a team we faced during this journey.</p><ul><li>Continue to maintain and support existing products and customers</li><li>Budget, time and resource constraints</li><li>Unknown scope of work</li><li>Product feature parity</li><li>What to modernize, where to start and how far we can go</li></ul><h4><strong>Planning &amp; Execution</strong></h4><p>“Plans are nothing; planning is everything” is a famous quote by former US President Dwight D Eisenhower (1890–1969). I always appreciate the fact that if you plan better, you execute with confidence.</p><p>During the initial few weeks, we came together as a team and brainstormed every possible option we could think of. We discussed what technology to use, how to maintain the code, resource requirements, learning curve around new technology, the scope of work, dev and test infrastructure requirements, etc. All the above activities were conducted in parallel while continuing the support our existing product.</p><p>As the scope of work was unknown, there was a lot of ambiguity and resistance among developers related to where to start, we decided to have a spike on those unknowns. For those who don’t know what spike is</p><p>“In agile software development, a spike is a user story for which the team cannot estimate the effort needed. In such a case, it is better to run time-boxed research, exploration to learn about the issue or the possible solutions. As a result of the spike, the team can break down the features into stories and estimate them”</p><p>During this phase, we discussed and agreed on technology selection, which container technology we will be using along with how we will build and manage the container images in the customer environment. One of the things we adopted in this phase is the document first approach. As a team, we agreed that we will document whatever technical challenges we faced along with probable solutions.</p><p>Another important thing to share is we started spike work with a small team that was dedicated for this work. Later, when we had a good understanding and path forward, we gradually added more horsepower to the team so that newly added members can jumpstart on the remaining things. We timeboxed this phase to a couple of sprints.</p><p>As we completed spike work for most of the items, we had a good understanding of the scope of work. We created stories and tasks as a result of spike work for tracking &amp; prioritization purposes. We prioritized the development work along with QE activities. Spike work gave us confidence and we knew the scope of work for most of the open items. We created a high-level plan and discussed with our leadership team and tentative release date for the first version.</p><p>We followed an iterative and incremental development process with internal milestones for delivery.</p><h4><strong>Conclusion</strong></h4><p>As I finish this blog, I can confidently say we are ready to deliver the first version of our product very soon. Although we are ready to release the first version, our journey doesn’t stop here. This is just the beginning of the road to product modernization, and this is a never-ending journey.</p><p>Product modernization should be a continuous and ongoing process. Business needs to invest in continuous product modernization that will empower them to adequately scale. Remember that this is not a one size fit all process, rather, product modernization is a multi-step process that starts with assessing and analyzing an existing application and having a defined roadmap.</p><p>Modernization is no longer a luxury: It’s a necessity. Please provide your feedback and suggestions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a70c40cce34" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>