Application Darwinism - Why Most Enterprise Apps Will Evolve to the Cloud

  • Published on

  • View

  • Download

Embed Size (px)


Application Darwinism - Why Most Enterprise Apps Will Evolve to the Cloud From AWS re:Invent 2013


<ul><li> 1. Application Darwinism - Why Most Enterprise Apps Will Evolve to the Cloud Brad Schick, Skytap </li></ul> <p> 2. Agenda Hybrid apps overview Demo Panel: F5 Networks, DataXu Q&amp;A 3. The architectural choices that support the development and deployment of cloud applications affect quality and timeliness, and can be the difference between success and failure. Mark Driver, Gartner Nov. 5 2013 4. Greenfield Applications Hybrid Infrastructure Not always Applicable Not often Sufficient 5. SvcApplication Hybrid Application 6. Point 1 Businesses want to leverage and extend their existing investments 7. Point 2 New computing technologies almost always augment, rather than replace, existing technology Mainframes ~1965 Client Server ~1985 Service Oriented ~1995 Cloud Computing ~2005 8. 96 of the worlds top 100 banks 71% of global Fortune 500 companies IBMs most profitable business line 23 of the 25 top US retailers Mainframes are still with us Image source: 9. Browsers are just the latest user interface for mainframes Loosely translated IBM quote 10. SOA (Service Oriented Architecture) 11. SSOA (Sorta Service Oriented Architecture) 12. Point 3 Production software must often be designed to work well in the cloud 13. Option 1: Punt Eventually, disregarding the advantages of the cloud will benefit your competition. 14. Option 2: Private Cloud Often just on-premises virtualization. Provides value, but the benefits are not a superset of what the cloud provides. 15. Option 3: Hybrid Apps A hybrid application spans multiple infrastructure and cloud locations, making use of resources and services from each. Components of the application may run on-premises or in the cloud. 16. Isnt that a Hybrid Cloud? No, a minimal hybrid application just has one service or component running in the cloud. 17. Candidates for migration Services or components that aren't meeting scaling needs Services with quick payback through reduced costs New opportunities: Things you can't do easily on your own infrastructure Services benefiting from global reach and reduced latency to end-users Non-production workloads such as development &amp; test labs 18. Qualities to seek out Aligns with corporate security and compliance policies Self-contained and loosely coupled to other services Not sensitive to latency between remote services Idempotent protocols between services (tolerant of network hiccups) Already scale out and fault tolerant 19. Challenges you may face Lack of federated authentication and authorization New deployment strategies Different monitoring and alerting strategies Various data placement decision (close to where it is used) Need for new IPC mechanisms 20. Most enterprise applications will evolve to the cloud Enterprise migration to the cloud should focus on the creation of hybrid applications rather than hybrid infrastructure This still isnt easy, but purpose built services like Skytap are emerging to help move specific workloads to the cloud Summary 21. Demonstration Fast and repeatable creation of complex dev/test environments Easy cloning and sharing of complete environments Support for existing continuous integration and build tools Deep visibility and control of resources for IT departments Built-in team collaboration Skytap helps dev/test teams become more efficient 22. Get your Skytap trial at: CTO &amp; VP of Engineering. Brad Schick CTO &amp; VP of Engineering, Skytap, Inc. *Image courtesy of DaMenace through Uncyclomedia Commons 23. Watch this Sessions Video Click Here: </p>