Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Why Your Digital Transformation Strategy Demands Middleware Modernization

799 visualizaciones

Publicado el

Your current middleware platform is costing you more than you think. It wasn't designed to support high-velocity software releases and frequent iteration of applications—prerequisites for success in today’s world. A new, modern approach to middleware is needed that enables both developer productivity and operational efficiency.

Join Pivotal’s Rohit Kelapure and Perficient’s Joel Thimsen as they discuss:

- The limitations of traditional middleware
- The benefits of middleware modernization
- Your options for modernization, including a cloud-native platform
- Tips for overcoming some common challenges

Presenters: Rohit Kelapure, Pivotal, Joel Thimsen, Perficient & Jeff Kelly, Pivotal (Host)

Publicado en: Tecnología
  • Sé el primero en comentar

Why Your Digital Transformation Strategy Demands Middleware Modernization

  1. 1. © Copyright 2018 Pivotal Software, Inc. All rights Reserved. Rohit Kelapure, Principal Solution Architect Pivotal @rkela Joel Thimsen, Director Cloud Strategy, Perficient @joelthimsen Middleware Modernization Trends & Best Practices
  2. 2. Life is like a box of chocolates … you never know what you're gonna get The Middleware Jungle
  3. 3. “Your Middleware Platforms Are Costing You More Than You Think”
  4. 4. Your Digital Transformation Strategy Demands Middleware Modernization Shift to the Cloud Digital Business Shrinking IT Budgets Integration Platforms Application Platforms MACRO TRENDS MIDDLEWARE PLATFORMS PROBLEM SOLUTIONS Cloud Native Platform Containers iPaaS Public Cloud DIY Platform
  5. 5. The Shades of Middleware API Management B2B Software Application Server Portal Message Oriented Middleware Enterprise Service Bus PaaS In-Memory Data Grid Complex Event Processing TODAY’S FOCUS Integration Middleware Application Middleware Java Centric
  6. 6. What is Application Server Middleware ?
  7. 7. Middleware Market Trends Digital business disruption has changed the application platform and integration market Shift towards lightweight infrastructure with cloud-native & open source leading the way API economy, microservice architecture, AI, and event processing are pushing existing application platforms. Middleware must shift to support digital value at scale GROWING SLOWING aPaaS iPaaS ESB Source: Gartner AIM 2018 Forecast App Servers Integration Brokers In-Memory Data Grids MOM Complex Event Processing API Management
  8. 8. Why should I care? The Problem Opportunity
  9. 9. Developer Disempowerment Software Delivery Performance Pain Points Deployment frequency For the primary application or service you work on, how often does your organization deploy code? Languages, Tools, Low-code IDEs, Legacy Programming models, Startup Time, Vendor Lock-In, Lack of choice Lead time for changes For the primary application or service you work on, what is your lead time for changes (i.e. how long does it take to go from code commit to code successfully running in production? Server Provisioning, Installation, Configuration drift, Runtime Bloat, License Cost , Patching, Service fix quality, Time to restore service For the primary application or service you work on, how long does it generally take to restore service when a service incident occurs (e.g., unplanned outage, service impairment)? Cloud Native Practices, Modern Security Protocols, Heavyweight monolithic stateful Change failure rate For the primary application or service you work on, what percentage of changes results either in degraded service or subsequently requires remediation (e.g., leads to service impairment, service outage, requires a hotfix, rollback, fix forward, patch)? Release Management, Lack of Continuous Deployment, Agile Practices, chaos engineering
  10. 10. The Pain of Enterprise Middleware Processes
  11. 11. Dependence on Manual Activities • Complex processes difficult to automate • Automation requires debt reduction • Platforms typically not designed for automation Non-optimized Delivery Process • Waste in delivery process • Lack of system efficiency only sub-optimization • Complexity drives defects Culture of Manual Intervention Organizational Silos • Not a culture of shared responsibility • Devs & Ops operating in silos • Difficult to release to production Release Train Low Value Tasks Manual Steps Working Silos
  12. 12. Modernization Opportunity Source: Forrester Total Economic Impact of Pivotal Cloud Foundry, October 2017 Attract & Retain Talent Increase Delivery Velocity Avoid Digital Disruption Opportunity Cost Current Value Potential Value BEFORE AFTER 1 to 2 releases per month Daily or weekly releases
  13. 13. Take Me Home … Solutions
  14. 14. Containerization Public Cloud DIY Platform iPaaS Cloud Native Platform Solution Overview
  15. 15. [ 1 ] Public Cloud “Do It Yourself” Platform DIY Cloud Native Platform ● Oversimplification ● Underestimating ongoing investment ● Thinking the Platform is Done ● The Lock-In Bogeyman Pivotal Cloud Foundry ● Increase Time to Value: Abstractions ● Full Lifecycle Engineering: Platform & Apps ● Complete: Ecosystem, Roadmap, Velocity, Maturity ● Curated Open Source: Multi-Cloud
  16. 16. [ 2 ] Integration Platform as a Service (iPaaS) Integration Master Data API Management Platform Application Integration ETL B2B / EDI Master Data Management Data Quality User Security Integration Engine Environments Business Rules
  17. 17. iPaaS Solution View Source: Dell Boomi HIMSS 2017
  18. 18. [ 3 ] Containerization Source: Gartner Blogs - Microservice Guts on the Outside Discovery Routing Service Mesh Orchestration Automation Monitoring ...Container 1 Load Balancing Execution Env Container 2 Load Balancing Execution Env Container n Load Balancing Execution Env API Gateway Use containers for apps that not marked for significant re-write Provides portability between environments and platforms Kubernetes provides great container orchestration capabilities but not enterprise ready platform Kubernetes learning curve can be significant for traditional operations teams
  19. 19. Storage NetworkingCompute Dev / Apps App User IT / Ops > kubectl Kubernetes Dashboard Load Balancing / Routing Container Image Registry App Monitoring App Logging OS Updates OS Images K8S Updates K8S Images Log & Monitor Recover & Restart Backup & Restore External Data Services Cluster Provisioning Provision & Scale Command Line / API Management GUI Monitoring GUI ...but Kubernetes alone is not enough for enterprises
  20. 20. Case Study: Running WebLogic (MedRec) and WebSphere (DayTrader) on K8s The WebLogic operator is a pain to setup, mostly because of configuring persistent volumes, but it works. Autoscaling worked as expected, however, upgrading the operator itself is a clumsy process that including moving traffic from on WebLogic domain to another. Furthermore, upgrading an application within a WebLogic domain on k8s doesn’t benefit from all the operational benefits of k8s (i.e. same upgrade path on WebLogic on VMs). WebSphere Liberty Helm chart has a bug that does not allow for upgrades when using Stateful Sets. Requires patching the helm chart to include an Update Strategy. Documented in current liberty helm chart recipe. The liberty helm chart assumes that there is an ingress controller based on NGINX and creates the ingress resource based on this assumption. Loading a secound ingress controller seems to resolve this. Adding more state to the application in the form of XA transactions and in- memory/overflow cache, upgrading of PKS, NSX-T, or the Helm Chart did not affect application SLO when deployed via the liberty helm chart. Level up in PKS Do rolling deployments Autoscaling Environment Specific Configuration Management control using 12-factor approach with configmaps and secrets Batch Process Guidance Guidance for Integration across microservice environments (PKS, PCF, Legacy)
  21. 21. [ 4 ] Cloud Native Platform
  22. 22. Spring Cloud Data Flow puts powerful integration, batch and stream processing in the hands of the Java microservice developer Spring Cloud Data Flow uses the Spring Cloud Stream project to construct its streams. Spring Cloud Stream builds upon Spring Boot to create DevOps friendly microservice applications Transformation: Integration with Spring Cloud
  23. 23. Transformation Case Study : Dismantling ESBs 1 2 3 4 5
  24. 24. Transformation Case Study: Replace Hardware Gateway & Integration Bus with Spring Cloud Stream & DataFlow Current State: ● Datapower used for interfacing with the external systems ● Data transformation with datapower causing limited horizontal scalability ● Slow development cycles and not easy to use in the context of modern agile development practices such as TDD, CD … etc. ● Integration Bus used to coordinate communicate between the store HW instances an the provincial DIS systems ● Limited horizontal scalability Recommendation: ● Implemented data transformation in stateless horizontally auto scalable scalable spring boot apps orchestrated with Spring cloud data flow running on PAS ● Leverage Spring Cloud Stream to replace Integration Bus flows with Spring Cloud stream apps coordinated by spring cloud data flow on PAS Impact ● Accelerate development velocity and reduce technical complexity ● Eliminate an proprietary technology with an Open Source Solution that is optimized for developer productivity, testability, and continuous delivery 25
  25. 25. Modernization : DDD Driven Decomposing Monoliths Techniques Working Code Slices Patterns OKRs Event Storming Slice Analysis Boris Snap/SnapE Implementation Patterns rinse&repeat Direction / Stay on Track Business Flow / Potential Slices Event Flow / Inform Architecture Small Pieces of Functionality Size / Risk Repeatable Recipes
  26. 26. Domain Event Domain Event Domain Event Domain Event Domain Event Domain Event Domain Event Domain Event Domain Event Domain Event Domain EventDomain Event Domain Event Domain Event Aggregate Command Command Aggregate ! ? Bounded Context Slice Candidate Policy Vehicle Modernization: Domain Model and Slice Candidate
  27. 27. Modernization Case Study: Decomposing Services Event Storming to drive out WebSphere Commerce order- calculation slice of functionality
  28. 28. Modernization Use Case: 1M LOC Insurance Domain Monolith
  29. 29. Are We There Yet ?
  30. 30. Barriers To Cloud Native Internal resistance to cloud-native approach Lack of cloud skills 65% 58% 62%70% Legacy infrastructure challenges Lock-in, existing vendor contracts According to 2017 study by a global technology consultancy
  31. 31. Middleware Transformation Journey Markers ? 1. % of middleware portfolio running on the cloud 2. Formal knowledge base of Application Migration assets 3. Cloud native developer and architecture enablement 4. App Transformation decisioning framework (aka "funnel") in place 5. Automated application development path-to-production 6. Developer Engagement - NPS, DAU, MAU, Power curve, Cohort analysis metrics 7. Application Portfolio Financial View of Assets
  32. 32. Cloud Native Applications on PaaS - Thinking in outcomes External Forces Technology Outcomes Pivotal-Enabled Capabilities Business Outcomes Application Outcomes
  33. 33. Scalability 500K Internet Facing Users (Go-Live in July) 300 Initial App Instances 2 Data Centers using vSphere in Active- Active deployment Security 21 Concourse Pipelines for automation of patches and upgrades. 23 CVEs fixed by Pivotal in 2018 and delivered as part of PCF 0 Information Risk Mgmt. issues to address Skills 6 Devs + 2 PMs 8-week App Tx expanding to 60* Customer Developers 5 Platform Operators trained during a 4- week Platform Dojo 1 Platform Team Stability 0 minutes downtime for running Apps in Prod & Dev. PCF environments 1 Major intra-day upgrade to PCF 2.1 with 0 downtime Consistent response times < 12ms Speed 90x Faster application release cycles 0 midnight monthly weekend outages for App releases 3 hrs to complete a major version PCF upgrade. Typical Pivotal Outcomes Savings: Faster Time-to-Market + Enabler to moving Apps to the Cloud Sustainability: Platform Dojo + App Tx + Balanced Account Team + SMEs
  34. 34. AppTx We are a team of consulting experts that jumpstart Application Transformation initiatives and quickly show measured wins. We use simple tools, start small and scale fast to redefine current systems and achieve cloud native speed, resiliency and economics. bit.ly/apptxpaper bit.ly/apptx
  35. 35. Pivotal + Perficient Relationship ● Industry Leading Cloud Native Development Platform and Tools ● Broad adoption across blue chip customers ● Technology Leadership ● Cloud Native Best Practices ● Robust Pivotal Cloud Native Ecosystem ● Pivotal Ready Advanced Partner ● 2018 Customer Impact Partner of the Year ● Certified multi-cloud platform expertise ● Deep Pivotal expertise and scale ○ 75+ certified PCF consultants ○ 150 Platform Acceleration Lab graduates in 12 months ● Cloud Native Application Development Strategies The strength of the Pivotal - Perficient partnership drives customer value by delivering significant business outcomes through thought leadership, next generation technology, modern software development methodologies and best practices.
  36. 36. Links & Resources Pivotal ● White Paper: An Inside Look at the Open Service Broker API: Easily Deliver Services to Cloud Foundry and Kubernetes ● Analyst Report: Forrester: Digital Transformation Requires Development Transformation ● Blog: In 2019, Put a Platform-as-a-Product Strategy in Place Perficient ● Website: Middleware Modernization ● Guide: Transform Your Application Development with PCF ● Partner Page: Pivotal and Perficient
  37. 37. Thanks
  38. 38. Transforming How The World Builds Software © Copyright 2018 Pivotal Software, Inc. All rights Reserved.

×