Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CloudExpo NY 2014: Moving Mission Critical Applications to the Cloud

891 views

Published on

A panel discussion on pitfalls and best practices for migrating mission critical applications to the cloud. I presented on June 12, 2014 with Shane Shelton from McGraw-Hill Education and Nathan Anderson from GE Capital

Published in: Technology, Business
  • Be the first to comment

CloudExpo NY 2014: Moving Mission Critical Applications to the Cloud

  1. 1. © 2014 Cloud Technology Partners, Inc. / Confidential 1 Cloud Computing Expo – NYC June 12, 2014 Moving Mission Critical Applications to the Cloud
  2. 2. © 2014 Cloud Technology Partners, Inc. / Confidential 2 • Kacy Clarke – Vice President, Principal Architect at Cloud Technology Partners • Shane Shelton – Sr. Director of Application Performance and Development Operations at McGraw-Hill Education • Nathan Anderson – IT Leader – Innovation at GE Capital About the Panel kacy.clarke@cloudtp.com www.linkedin.com/in/kacyclarke/ updraft-downdraft.blogspot.com @kacyclarke +KacyClarke
  3. 3. © 2014 Cloud Technology Partners, Inc. / Confidential 3 Cloud and Mission Critical is the New Normal
  4. 4. © 2014 Cloud Technology Partners, Inc. / Confidential 4 Modern cloud architectures are hard to manage and scale using traditional approaches The Mission Critical Application Dilemma Cloud Provider Customers Employees Application Source: Compuware XML/SOAPhttp SQL TCIP/IP
  5. 5. © 2014 Cloud Technology Partners, Inc. / Confidential 5 • Missed SLA’s • Long Mean Time to Recovery • Gaps in monitoring and operational tools • Sporadic performance problems • Data synchronization and placement issues • SDLC sprawl and inconsistencies • Over provisioning • Dev and operational skills and knowledge • Integration latency • Manual or frozen configurations • Compliance or security findings • Cost savings objectives not met Lift and Shift Can Result in Cloud Migration Debt
  6. 6. © 2014 Cloud Technology Partners, Inc. / Confidential 6 The Reality Check for Enterprise Application Migration
  7. 7. © 2014 Cloud Technology Partners, Inc. / Confidential 7 • What were some of the key business challenges you've faced in preparing to move to the cloud? • What are some of the key technical challenges in building your cloud environment? • How have you had to change your applications to run in the cloud? Panel Discussion: Mission Critical Application Migration Private Cloud Public Cloud Hybrid Cloud Multi- Cloud
  8. 8. © 2014 Cloud Technology Partners, Inc. / Confidential 8 GE: ArchOps – more than cloud
  9. 9. © 2014 Cloud Technology Partners, Inc. / Confidential 9 GE Continuous Convergence Aka: Full Stack Continuous Delivery Everything Converges
  10. 10. © 2014 Cloud Technology Partners, Inc. / Confidential 10 GE: Lessons from the journey so far… 1. Plan for Organizational & Culture Change; Communicate! 2. Velocity needs effective monitoring & alerting 3. Minimum Viable Product is essential: Building faster = better. 4. Requirements must be clear: code-able and testable 5. Empower your teams 6. Get developers powerful machines 7. Its not for everyone at first; keep going 8. Full stack engineers are hard to find…plan to grow them Our journey now continues with many more apps in the pipeline.
  11. 11. © 2014 Cloud Technology Partners, Inc. / Confidential 11 Biggest Business Challenges? MHE: Convincing a Large Organization to Move to AWS Is Hard • Cloud is still relatively new • Legacy applications in AWS is difficult • Operational support (monitoring, governance, policy/procedure) • Financials • Finding people
  12. 12. © 2014 Cloud Technology Partners, Inc. / Confidential 12 • Difficult Situations Encountered – Moving away from F5s to ELBs – Security approvals – Dependency on Oracle products – Not being in control of everything (IaaS instead of in-house) – Monitoring MHE: Our Biggest Challenges
  13. 13. © 2014 Cloud Technology Partners, Inc. / Confidential 13 • What Were the Most Difficult Hurdles to Overcome? – ELB functionality • Limited in what it is capable of doing when compared to internal F5s – Oracle Coherence for session management/caching • Was not made for the cloud; strict latency rules • Can only deploy across a single AZ; won’t scale multiple AZs – Auto Scaling • Using Weblogic and Coherence takes a lot longer to scale up a new server than expected (6-7 minutes) • Takes a really long time to automate things when you’re starting from scratch, especially when using proprietary software MHE Connect’s Biggest Technical Challenges
  14. 14. © 2014 Cloud Technology Partners, Inc. / Confidential 14 Aligning Your Application to the Cloud Isn’t a Simple Job Traditional Architectures • Scale Up • Monolithic • Stateful • Infra Dependent • Fixed Capacity • LAN Located dependencies • Latency intolerant • Tightly coupled • Consolidated / clustered DB • Rich / chatty client • Commercial licenses • Infra Supported Availability • Semi-automated build/deploy • Manual fault recovery • Active/Passive/DR • Perimeter Security • Allocated costs The “Old World” Cloud Aligned Architectures • Scale Out • Distributed • Stateless • Infra Agnostic • Elastic capacity • WAN, Location transparency • Latency tolerant • Loosely coupled • Sharded / replicated / distributed DB • Mobile/thin client • PaaS / Open Source • App Supported Availability • Continuous Integration/Delivery • Self healing, fault tolerant • Active/Active • Defense in depth • Pay as you go The “New World” The Targets Refactor Automate
  15. 15. © 2014 Cloud Technology Partners, Inc. / Confidential 15 • The Cloud makes it easy to get whatever resources you need on demand • Continuous integration and continuous delivery can deliver rapid innovation for all applications • Development teams have a self-service portal for all non-production environments • Automated provisioning ensures full security and compliance • Fully automated deployments are simple to roll back The Dream: Agile, Fully Automated, Compliant App Infrastructure
  16. 16. © 2014 Cloud Technology Partners, Inc. / Confidential 16 • The application team hires “DevOps” resources or outsources infrastructure deployment • They choose non-standard technologies, configurations • Core system monitoring is incomplete • Security and compliance standards are only partially implemented • No one is responsible for OS patches, capacity mgmt, or required upgrades • Operations has no visibility into the deployment as their agents aren’t running • Incident management procedures have only the dev team on call • Data movement jobs break and quickly get out of synch • A major issue can cause a several day outage • Performance issues emerge The Reality 1: App Team Driven Cloud Deployment
  17. 17. © 2014 Cloud Technology Partners, Inc. / Confidential 17 The Reality 1: Application Team Driven Cloud Migration
  18. 18. © 2014 Cloud Technology Partners, Inc. / Confidential 18 • The infrastructure organization creates a Cloud Management Group • They recreate their current tools and environment in the cloud • They require dev teams to use the current Service Request process • Automation is built separately by each of the “Towers” • The database team tries to opt out. So does the security team • Provisioning and changes still take hours or days • Innovation is constrained by current technologies and processes • The Dev Teams bypass them and outsource. See Reality 1. The Reality 2: Infrastructure Team Driven Cloud Deployment Network ServerSecurity Storage App Infra Database Operations Support
  19. 19. © 2014 Cloud Technology Partners, Inc. / Confidential 19 The Reality 2: Infrastructure Team Driven Cloud Migration
  20. 20. © 2014 Cloud Technology Partners, Inc. / Confidential 20 DevOps is Not Teaching an Old ITIL Dog New Tricks
  21. 21. © 2014 Cloud Technology Partners, Inc. / Confidential 21 Best Practices: Waste, Pipelines, Metrics and Automation Remove the silos, the wait queues and the waste Define Deployment Pipelines Automate, Automate, Automate Add logging, metrics and dashboards – including measuring your processes
  22. 22. © 2014 Cloud Technology Partners, Inc. / Confidential 22 • Leverage DevOps best practices to change how application teams work with operations • Treat cloud services like products • Continuous feedback and improvement cycles Best Practices: Agile/Lean + DevOps + SvcMgmt + SysOps Agile/Lean SDLC DevOps: Agile Infrastructure Cloud Service Management SysOps: Cloud Operations Network ServerSecurity Storage App Infra Database Operations Support Application Focus Cloud Focus Integrated Provisioning and Operations Platform Deployment Pipeline Metrics and CMDB SCM and Automation
  23. 23. © 2014 Cloud Technology Partners, Inc. / Confidential 23 Questions? Thank you for your time and interest. Kacy Clarke, VP / Principal Architect, Cloud Technology Partners @kacyclarke / kacy.clarke@cloudtp.com

×