![]() |
Nearly all of our clients who experiment with a Cloud Native approach for application development quickly become believers. The magnitude of change involved with DevOps, continuous delivery and PaaS platforms, however, drive most clients to start by dipping a toe in the water with one or two initial applications. Once clients are comfortable with going Cloud Native, a natural next question is around the legacy portfolio. Which applications would benefit from transformation to a true Cloud Native model? What path will be required to get them there? How much code will we have to rewrite? And what’s the business case for doing it? There are multiple options to consider. For some applications the Cloud Native modernization business case just won’t be there and a ‘strangler application’ pattern will be the best answer. In the strangler approach, the legacy app is isolated and exposed to new Cloud Native applications via API or service interface, providing ongoing access to business functionality. The application is slowly retired, or ‘strangled’ as new services are incrementally developed to replace the original app. For other applications a ‘lift and shift’ model can be used – for example Java applications that use standard libraries can easily be moved to Pivotal Cloud Foundry. For some the only option will be refactoring or rewriting the application for Cloud Native. Michael Cote of Pivotal has a great post that describes the various options and tradeoffs in more detail. Clients looking to operationalize and scale the Cloud Native model need to understand the different options and patterns and how they apply across their portfolios. In a recent post we discussed that the first step for enterprises driving portfolio transformation at scale is to profile the applications and first determine which are high potential modernization candidates (vs. migrate, retire or retain). With our Application Profiling services EMC brings a unique set of skills, experience and tools that even help even our largest enterprise clients rapidly identify the appropriate investment path for applications in their portfolio. Once clients have identified ideal modernization candidates, they need to go deeper into the application to assess Cloud Native readiness. To help our clients extend their analysis to include Cloud Native assessment we’ve recently added a new capability to our Application Profiling services. Our new Cloud Native Assessment service scans application code and within minutes provides an analysis of that application Cloud Native ‘readiness’ based on criteria aligned with the 12 Factor Model. Why is this valuable to our clients?
By extending our Application Profiling services to assess Cloud Native readiness, EMC Global Services can help clients identify the optimal cloud modernization strategy for their portfolio across the wide variety of options that exist. Contact us to learn more about how we can help. The post Assessing App Portfolios for Cloud Native Readiness appeared first on InFocus. |
