Zero Dollar Migration Program
Download as PPTX, PDF0 likes418 views
SpringOne Platform 2017 Rahual Deo, Mphasis There are many key elements a customer considers before moving to Pivotal. Two of the biggest barriers are Bubble Cost for migration & operating cost of Pivotal + Cloud. Our presentation will consists of multiple tracks which drastically lowers the cost of Pivotal migration, coupled with our creative engagement model which manages bubble cost issues.
Ad
More Related Content
What's hot (20)
Similar to Zero Dollar Migration Program (20)
Ad
More from VMware Tanzu (20)
Ad
Recently uploaded (20)
Zero Dollar Migration Program
- 1. 112 December 2017 | © Mphasis 2017 Proprietary and confidential information. Zero Dollar Cloud Modernization
- 2. 212 December 2017 | © Mphasis 2017 Proprietary and confidential information. AGENDA Why Modernization over Migration? What is Zero Dollar Cloud Modernization? Why should Enterprises adopt this Model? Steps for Modernization How to Pay for it? Q & A
- 3. 312 December 2017 | © Mphasis 2017 Proprietary and confidential information. Why Modernization over Migration? On-Premise Applications Data Runtime Middleware OS Virtualization Servers Storage Networking Infrastructure- as-a-Service (IaaS) Applications Data Runtime Middleware OS Virtualization Servers Storage Networking Platform-as-a- Service (PaaS) Applications Data Runtime Middleware OS Virtualization Servers Storage Networking VendorManages inCloud Expensive Infrastructure Client Manages Client Manages VendorManages inCloud ClientManages X Zero $ Modernization Lift & Shift Save $$$$ through migration Mode rnize Mode rnize Mode rnize Mode rnize Mode rnize No carry-over of Technical Debt No big bang approach Lower cost of execution Lack of Re-Usability Lower risk and no Disruption
- 4. 412 December 2017 | © Mphasis 2017 Proprietary and confidential information. What is Zero Dollar Cloud Modernization? 1 2 3 4 5 6 7 8 9 10 11 12Months Investment ReturnRepresentative ROI Break-Even Self funded Application Modernization Free up cash from expensive middleware Modernize at your pace Cloud enabled during modernization Harness the power of cloud native
- 5. 512 December 2017 | © Mphasis 2017 Proprietary and confidential information. Why should Enterprises Zero Dollar Modernization? Business value delivered at regular internals Time Shrinking the Core Technology Chassis Capabilities delivered at lower incremental cost Technology Chassis Traditional Big Bang Legacy Modernization Go Live Switch off Business Need Driven Modernization Capability vs. Application Driven Approach State of the Art to eliminate antiquated technology Consolidate applications based on capability vs Better TCO – During and After Modernization Legacy Strangulation happens incrementally State of the Art is tuned towards Optimal portfolio vs. Gold plated portfolio Chassis sets up future modernizations at lower incremental costs A mix of stabilized, optimized, standardized, rewritten, novelty applications Faster time to market Powered by Recipes of modernization Blueprints, Reference architectures for a quick start to modernization Eco-system of partners identified as part of Recipes for modernization Untethering Legacy Technical Debt Curve
- 6. 612 December 2017 | © Mphasis 2017 Proprietary and confidential information. Steps for Modernization Runs on PCF Runs well on PCF Runs Great on PCF Microservices / API First Re-platforming Phase Modernization Phase Transformation Phase (Iterative) • App will run using TomEE build pack • No File System Dependent Processes; will be replaced with S3 API • Configurations will be Externalized • Build Eng.. Tool (Gradle) • Spring Bootification • Self Contained App • Horizontally Scalable • Platform Managed Port and Addressing • Consumes Platform Services using Platform Semantics • Microservices will be carved out from the Monolith around the Functional Seams (one at a time) • Adequately Test Covered • CI/CD Tooling and Methodology • Design for Failure, Unaffected by Dependent Service Failure • Metrics and Monitoring baked- in • Cloud Agnostic runtime Implementation • Microservices • API First Design Final Phase
- 7. 712 December 2017 | © Mphasis 2017 Proprietary and confidential information. Steps of Modernization – Example Pre-Migration Architecture AIX Platform IBM CMS LOB Stag e HTTP / HTTPS / TCP / SSL Cache Management Connection Management Local Labels Custom Framework IBM HTTP Web Server IBM HTTP Web Server App Load Balancer Cache Management Connection Management Local Labels Custom Framework IBM WebSphere App Server IBM WebSphere App Server Documents Ware house App specific configuration Logging mechanism Connectional Pool Load management
- 8. 812 December 2017 | © Mphasis 2017 Proprietary and confidential information. Steps of Migration – Example Post-Migration(PCF) Architecture Java Container Self Contained App App Instance 1 Configuration User Provided ServicesLoggregator Pivotal Cloud Foundry Platform Oracle DB CMS Google Map Service Amazon S3 Log Management Tool User Data Store OAuth2 PCF Managed Services Platform Services Java Container Self Contained App App Instance 2 Platform Metrics
- 9. 912 December 2017 | © Mphasis 2017 Proprietary and confidential information. Steps of Modernization - Lift & Shift Considerations Dependencies PCF Remarks Container functionality/features Application has already been successfully tested on TomEE and JBoss Configuration Externalization Config file is used by the Application framework and need not be externalized to this migration Application Log With simple switch in the Application Configuration, log can be printed to system IO from where PCF will pick it up System Log Platform will take control of it Scalability/ Capacity management Spinning of additional instance to take care of additional capacity comes out of box from PCF. Session Management There is no session replication so PCF/Tomcat will take care of it Caching Caching will be handled at an application level and multi-country caching will be part of the consolidation effort
- 10. 1012 December 2017 | © Mphasis 2017 Proprietary and confidential information. Steps for Modernization– Path to Microservices Replatform to PCF Identify Bounded Contexts Build a Bounded Context Map Pick Bounded Context to refactor to Microservice Refactor a Bounded Context to Microservice Iterate until you reach the desired level of maturity Define Ports Define Event Define Adapters Define Testing Strategy Create Spring Boot project Integrate into CI/CD Write Tests Cut & Paste Refactor
- 11. 1112 December 2017 | © Mphasis 2017 Proprietary and confidential information. How to Pay for it? Hardware Head Units Configuration Web Servers 3 Servers(3 Instances) 2 Core x 16 GB RAM App Servers 3 Servers(4 Instances) 4 Core x 32 GB RAM DB Servers 3 Servers 4 Core x 32 GB RAM License Type Instances Remarks WebSphere (PI/TomCat EE) 3 servers (7 app instances) 42 – Prod for 21 countries & 28 Non prod Oracle Database 3 databases - ~ 55 Schemas 1 – 1 replication prod DB & 1 Non prod DB Type Instances Supported Coverage Middleware 70 Instances(7 Instances) 24 X 7 DB 3 instances, Active – Passive DB 24 X 7 Ops Cost/Yr $ 104,000($ 57,600) $ 205,200($ 57,600) $ 205,200($ 49,200) Cost/Yr $ 500,000($ 175,000) $ 100,000($ 175,000) Cost/Yr $ 1,008,000($ 46,200) $ 54,000($ 54,000) $ 514,400 ($ 133,200) $ 600,000 ($ 250,000) $ 1,062,000 ($ 100,200) Total Infra cost per year – $2,176,400($483,400) 75% Savings Example Before and After Cost * Mphasis has an offering where TCO ownership could be assumed during the phase of modernization.
- 12. 1212 December 2017 | © Mphasis 2017 Proprietary and confidential information. F A Q Q. Do I have to build a 12 factor Application to run on PCF? A. No. It is not mandatory. Q. Can I migrate my application to PCF? A. Yes. Applications which follow certain architecture patterns can be migrated to PCF. Q. Do I have to re-write my application to run on PCF? A. No. If the application follows certain architecture patterns then only minor configuration changes would be needed. Q. Do I need a PCF AI(App Instance) for each of my Microservices? A. Depends on the definition of Microservice.
- 13. 1312 December 2017 | © Mphasis 2017 Proprietary and confidential information. Q & A
- 14. 1412 December 2017 | © Mphasis 2017 Proprietary and confidential information. THANKYOU About Mphasis Mphasis (BSE: 526299; NSE: MPHASIS) enables customers to reimagine their digital future by applying a unique formula of integrated cloud and cognitive technology. Mphasis X2C2 TM formula for success, (shift anything to cloud and power everything with cognitive), drives five dimensions of business value with an integrated consumer- centric Front to Back Digital Transformation, enabling Business Operations and Technology Transformation. Mphasis applies advancements in cognitive and cloud to traditional application and infrastructure services to bring much needed efficiency and cost effectiveness. Mphasis’ core reference architectures and tools, combined with domain expertise and hyper specialization are the foundation for building strong relationships with marquee customers. Contact with us on www.mphasis.com Important Confidentiality Notice This document is the property of, and is proprietary to Mphasis, and identified as “Confidential”. Those parties to whom it is distributed shall exercise the same degree of custody and care afforded their own such information. It is not to be disclosed, in whole or in part to any third parties, without the express written authorization of Mphasis. It is not to be duplicated or used, in whole or in part, for any purpose other than the evaluation of, and response to, Mphasis’ proposal or bid, or the performance and execution of a contract awarded to Mphasis. This document will be returned to Mphasis upon request. [email protected]
Editor's Notes
- #2: 1. Zero Dollar Migration Program · There are many key elements a customer considers before moving to Pivotal. Two of the biggest barriers are Bubble Cost for migration & operating cost of Pivotal + Cloud. Our presentation will consists of multiple tracks which drastically lowers the cost of Pivotal migration, coupled with our creative engagement model which manages bubble cost issues. · Audience for such session would be primarily senior management – CXO’s, business & Directors or Senior architects.
- #3: Good Afternoon everyone! I am here to deliver 3 key takeaways today 1st, Why cloud modernization over cloud migration 2nd, What specific steps you need to take And 3rd, How do you make the economics work
- #4: Why cloud modernization instead of cloud migration? No carry-over of your technical debt - Once the application is modernized, application will be completely new from the architecture design perspective No big bang approach - Instead of one time big upgrade we recommend modernization be spread over a period of time with smaller deliverables. This will also enable no-downtime. Lower cost of execution - We focus primarily on getting value in smaller chunks while upgrading the core architecture. Lower risk - Since the changes are performed in smaller chunks risk of execution is also pretty low.
- #5: What is $0 dollar modernization? Free up cash from expensive middleware - This approach works very well with applications which use the likes of WebSphere and WebLogic as their application containers. Use the free cash to fund Application Modernization - This is an approach which allows modernization without any additional budgetary support. Other resulting benefits of this approach Modernize at your own pace - Since the application is migrated to cloud at the very first step, there is no organization pressure of being cloud-enabled. Also knowing that in-production applications are critical in nature execution can be spread over a period of time. Spreading over time also ensures no disruption. Cloud enabled during modernization - Applications are migrated to the cloud at the very first step. This way application is always available in the cloud while it is been modernized. Harness the power of cloud native - End objective of this modernization approach is to harness the power of native technologies offered through the cloud platforms.
- #6: Why should enterprises adopt this model? Business Need Driven Modernization We take the capability based approach during the re-designing of the architecture. These capabilities would belong to a domain, enabling re-usability across enterprise. This process also eliminate, antiquated technologies from the application architecture Better TCO Lower technology debt results to lower overhead Lower risk results in higher yield for your investment Faster time to market Pre-conceived execution plans and standardized architecture patterns allow faster time to market Let's compare these two charts here What you see on the left side is the traditional big-bang approach. Here you build everything at once and go-live. This kind of approach is expensive and adds lot of risk to the system What you see on the right is an approach where we build the system incrementally. A technology chassis, is built which works as the foundation for the long term demand of the system. As said earlier features are extracted out of the old system and capabilities are added to this chassis. If you follow the red curve you will see that technical debt goes down and new system gets build.
- #7: Steps for modernization There are 4 stages to this process Re-platform - As a 1st step we migrate the application to PCF. It is very similar to cloud lift & shift. But the advantage here is, it runs on PCF at a very early stage of the modernization journey. Modernization - At this stage we start applying offerings of Spring and PCF e.g. Spring Boot Transformation - We carve out capabilities and start building independent Microservices. This also opens the application for external consumption Microservices / API First - At this final stage the monolithic code would have been deconstructed and application is ready to enjoy the features of new architecture
- #8: Example of pre-migration Application Architecture You can see here that WebSphere has been used as an application container Also Websphere requires that it run on the AIX platform There are bunch of other services which are not tightly-coupled to the core application
- #9: Example of post-migration PCF Architecture Earlier I shared how a WebSphere architecture looked on AIX On this slide you can see how the architecture looks within PCF. This is almost L&S but the application is running on PCF You can see PCF services available to the application. Not used at this stage but still available for all future demand
- #10: Lift & Shift considerations You can see log, session, caching etc. in this list Rule of thumb is to remove all the dependencies from the underlying operating system This way application is ready for cloud enablement Let me quickly walk you through this list
- #11: Iterate to Microservices/API First This is a sample process of building capabilities. It is repeated till the application is 100% Microservices enabled. Post that all updates are done following the "API First principles".
- #12: How to pay for it? There are 3 parts to the free cash flow 1. hardware, 2. license and 3. Ops In this example you can find a savings of 75%(which is approximately $1.5M) If you look at the %-savings from each of these groups, operations contributed most of the savings
- #13: I hope I was able to deliver 3 messages I mentioned at the beginning of the session. Before moving to the Q&A let me answer some of the questions frequently asked by my clients F A Qs Q. Do I have to build a 12 factor Application to run on PCF? A. No. It is not mandatory. Q. Can I migrate my application to PCF? A. Yes. Applications which follow certain architecture patterns can be migrated to PCF. Q. Do I have to re-write my application to run on PCF? A. No. If the application follows certain architecture patterns then only minor configuration changes would be needed. Q. Do I need a PCF AI(App Instance) for each of my Microservices? A. Depends on the definition of Microservice.
- #14: F A Qs Q. Do I have to build a 12 factor Application to run on PCF? A. No. It is not mandatory. Q. Can I migrate my application to PCF? A. Yes. Applications which follow certain architecture patterns can be migrated to PCF. Q. Do I have re-write my application to run on PCF? A. No. If the application follows certain architecture patterns then only minor configuration changes would be needed. Q. Do I need a PCF AI(App Instance) for each of my Microservices? A. Depends on the definition of Microservice.