Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo

Microservices Expo: Article

SOA World - Legacy Systems, The Risks & Misconceptions

The risks & misconceptions

One of a CIO's top priorities is to leverage information to enable better business decisions and outcomes. Many CIOs trace constraints on their business back to the limitations of older legacy information systems - specifically, outdated applications.

A legacy-based environment can make it difficult to attain the level of agility, flexibility, and responsiveness that growing enterprises need from their applications. For many organizations, the application has become the business - powered by technology. Modernizing applications is a key step to providing agility and lower cost of ownership, as well as creating a Service Oriented Architecture (SOA) and ultimately, accelerating business outcomes. However, modernizing also presents risks - both in the process and the final result.

To manage the transition safely from costly and inflexible application architectures to increased application agility - which is aligned to and able to respond to business demands flexibly - there are critical steps that enterprises must take. Through a modernization process, enterprises can build a flexible and manageable application environment that can take advantage of an SOA and shared IT infrastructure, to make the best use of their company's most valuable resources: people and information. Application modernization uses services and technologies to reduce computing costs and improve IT service delivery, while enhancing customer service and knowledge-sharing capabilities.

This article will describe drivers for modernizing applications, the common misconceptions, and critical steps businesses should take to safely modernize applications to create a path to SOA.

Why Modernize Applications?

  • Business Technology: The new era of business technology represents a shift from information technology as a separate department to a model where technology powers the business. With it, the CIO is now also accountable for overall business outcomes such as managing risk, accelerating growth, or lowering costs. IT risks are now business risks, and IT opportunities are now business opportunities. By modernizing applications, the CIO can keep IT running smoothly, create new areas of innovation, and be an asset to the company.
  • Innovation and Cost Savings: Today companies spend the majority of IT resources on application maintenance and support, leaving a much smaller portion for business innovation via IT. By modernizing applications, IT departments can achieve significant cost savings and devote that resource to innovation.
  • Desire for IT agility: This desire is also driving organizations to modernize applications. An agile software infrastructure directly serves the needs of the business as well as the IT function, but it's proven that the business can have the most to gain. By reducing the lead time for application changes and by creating flexible, agile systems, the business can get the response from their IT systems that they've always demanded. Added to this is the cost savings that can be redirected from maintenance functions - up to 70% of IT costs in many organizations - to that of business innovation.
  • SOA is inevitable and will be a key architectural approach in the future: Modernizing applications is a key step to creating an SOA. Companies today continue to invest in SOA to respond quickly to regulatory and competitive pressures. They also continue to adapt business processes to keep pace with market change. It's important to approach SOA with a combined software and services effort that provides a comprehensive foundation for successful adoption of SOA.

    To achieve these outcomes effectively, CIOs need greater visibility into their application environment.

    Modernization Fears
    While most IT organizations are painfully aware that they have applications and systems that are underperforming, most aren't eager to undertake a modernization effort. There are several misconceptions surrounding modernization:
    1.  "This could compromise the service levels I'm accustomed to." Many times a senior IT executive will wonder, "If I move this piece of software from my legacy environment to a new system, will I get the same service levels?" Companies are hesitant to make the move and modernize their applications because they're unsure if the new system will garner them the same benefits.

    The key here is to understand which attributes of the legacy system are critical to the business need and ensure that the functionality and underpinning infrastructure deliver and exceed the quality of service that the business demands. The secret is not to 'blindly' move all of the legacy software to a new platform, but to assess what software is required and what can be replaced or discarded. It's worth pointing out that when the original legacy system was built, much of the functionality had to be written in code by hand. Whether it's using packaged software or operating system functionality, we can reduce the amount of handwritten code, thus providing a much lower risk to modernization.

    2.  "Modernizing applications is costly." Some CIOs aren't aware of the return on investment (ROI) that modernization can produce. Many IT leaders erroneously assume modernization requires a complete rebuild to achieve strong ROI, and very often that isn't the case.

    3.  "This will cause operational disruption and my business cannot afford that risk." CIOs fear that the shaky application "house of cards" they've built might crumble if it's revamped. They worry about potential security flaws, system downtime, and exposure to technical failure.

    Part of any modernization effort is the transitional planning, which has to be based on a thorough assessment of the current state. The better we know the current environment and its linkages to other application components, the lower the risk in the transition. Once again, going in blindly is exactly the wrong strategy.

    Steps to a Smooth Modernization
    With the software environments customers have today, modernizing isn't a one-size-fits-all proposition. Unless the organization knows what must be done, and does it consciously, the change will have no meaningful effect. There are several key steps to consider when modernizing a company's legacy systems:

    1.  Take inventory: You've recognized that to achieve business goals, you need greater visibility into your application environment. The first step is to take an inventory of your applications - identify, analyze, and report on the status of the portfolio of applications in your environment.

    2.  Prioritize: To prioritize the application modernization project, CIOs should evaluate the existing architecture and constituent applications, review applications that may have differing characteristics, and examine historical and anecdotal information to determine the level of business value and technical quality of each application. Next, it's important to examine the potential costs and revenue impact of modernization for each application, and then rank and categorize each application as you discuss the best approach to take. Finally, identify those applications best poised for modernization and establish a target architecture.

    3.  Create a detailed action plan: Do a detailed analysis of the applications you've decided to modernize. This process focuses on specific applications and their underlying architecture - with a thorough examination of all the issues that affect three major tasks: 1.) existing application decomposability and cost impact on mining existing code; 2.) targeted application options including hardware, software, operating system, monitoring, management, and development; and 3.) incremental modernization strategy to move from the existing architecture to your target architecture, while allowing both to coexist during the transition.

    4.  Transition your apps: Once the roadmap is in place, the next step is to bring legacy applications up to today's performance standards while having a minimal impact on day-to-day business operations. These steps include re-engineering, re-hosting, replacing, retaining and retiring, as well as building, testing, and maintaining the new application environment.

    5.  Finally, it's important to implement management and support best practices to transition smoothly to the new operational environment.

    Application Modernization Is a Must
    Legacy systems stall innovation and are costly to maintain, but as any business professional knows, they run today's business. Modernizing applications isn't impossible if you plan properly. As a prerequisite for staying competitive in this global economy, IT modernization is a must-do for enterprises.

    Companies are understandably concerned about the cost of modernizing its applications, the level of service during and after the move, and the possible exposure to technical failure. However, with proper planning and experience, it's possible to transition smoothly from legacy systems to an architecture that's more agile and responsive.

    Enterprises should take an inventory of their application environment, and prioritize the most important and cost-effective applications. They can then analyze and determine the best course of action. Once a plan is in place, companies can begin the actual modernizing process through re-engineering, re-hosting, replacing, retaining, and retiring. Finally, a strong management and support system is key to a smooth transition.

  • More Stories By Mark LaJeunesse

    Mark LaJeunesse is the service-Oriented architecture (SOA) program manager for Hewlett-Packard Services' Consulting and Integration business. He is responsible for the development of SOA Services, Sales and Delivery Training, driving HP's EAS SOA visibility and differentiation in the market. Mark has 20 years of experience in the high-tech industry.

    More Stories By Paul Evans

    Paul Evans runs the Worldwide Practice for Application Modernization for HP Services. He has worked within the IT industry for many years, starting his career as a software developer before moving to positions with Digital, Compaq and now HP. He has a 'passionate' interest in the future applications and their inherent architectures focusing on the business benefits that this technology can bring. This started with his work on the adoption of Ethernet-based networks through client server to his current responsibility. Paul lives in the north of England.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    @MicroservicesExpo Stories
    The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
    "Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
    Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
    "CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
    Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
    "This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
    "We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
    Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
    The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
    While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
    Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
    Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
    DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
    We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
    "Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
    identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...