Architecting the Cloud: How EAs should think about Cloud Computing

1. Architecting the Cloud: How EAs should think about Cloud Computing Pratheesh T S

2. Pratheesh T S Introduction How many of you are Enterprise Architects?

3. Agenda • Enterprise Architect role • Cloud Computing • Cloud Types and different trends • Considerations: Architecting Cloud • Example: BPOS\ Office 365 and AWS • Questions

4. Enterprise Architect • Alignment of IT strategy with company's business goals. • Optimization of information management approaches based on evolving business needs and technology capabilities. • Long-term strategic responsibility • Promotion of shared infrastructure and applications to reduce costs • Management of the risks associated with information and IT assets through appropriate standards and security policies. Business People Process Technology

5. Cloud Computing Software As Service Platform As Service Infrastructure As Service …………… As Service

6. Cloud Computing Where do your application "Live“? • On Premises • Hosted • Cloud

7. Cloud Computing • Application runs • on-premises • My own hardware, connectivity, software, etc. • Complete control • Complete responsibility • Upfront capital costs for the infrastructure

8. Cloud Computing Application runs on-premises Buy my own hardware, and manage my own data center • Application runs • on-premises • Bring my own machines, connectivity, software, etc. • Complete control and responsibility • Upfront capital costs for the infrastructure Application runs at a hoster Pay someone to host my application using hardware that I specify • Application runs at a hoster • Rent machines, connectivity, software • Less control, but fewer responsibilities • Lower capital costs, but pay for fixed capacity, even if idle

9. Cloud Computing Application runs on-premises Buy my own hardware, and manage my own data center • Application runs • on-premises • Bring my own machines, connectivity, software, etc. • Complete control and responsibility • Upfront capital costs for the infrastructure Application runs at a hoster Pay someone to host my application using hardware that I specify • Application runs at a hoster • Rent machines, connectivity, software • Less control, but fewer responsibilities • Lower capital costs, but pay for fixed capacity, even if idle Application runs using cloud platform Pay someone for a pool of computing resources that can be applied to a set of applications • Application runs using cloud platform • Shared, • multi-tenant environment • Offers pool of computing resources, abstracted from infrastructure • Pay as you go

10. What is Cloud “Pool of computing resources offered by a vendor, typically using a “pay as you go” model” “A pool of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption” “A standardized IT capability, such as software, app platform, or infrastructure, delivered via Internet technologies in a pay-per-use and self-service way”

11. Defining Cloud Type • Public Cloud • Multi tenant Pool of computing resources offered by a vendor , typically using a "Pay as you go" model • Hybrid Cloud • Combination of Public or Private cloud and On premises • Private Cloud • Pool of Computing resources that lives within a self managed datacenter • Pool of computing resources that lives within a datacenter with no sharing

12. Iaas and Paas Email LOB app Native Cloud app PaaS IaaS

13. Gartner’s View of Clouds

14. “By 2012, 80% of Fortune 1000 enterprises will be using some cloud computing services, 20% of businesses will own no IT assets.” “The bottom line: Early adopters are finding serious benefits, meaning that cloud computing is real and warrants your scrutiny as a new set of platforms for business applications.”

15. Maturing Software Segments Some PaaS\ SaaS offers are already quite mature; some others are emerging

16. Global Cloud Market Landscape

17. Considerations: Cloud • Lower cost: CAPEX, OPEX • Greater agility • Match capacity to demand • How to leverage on-premises, public, private and dedicated cloud • Privacy of data • Latency/performance considerations • Meet requirements for secure communication and compliance • Increase speed to market • Handle complexity of SLA

18. Considerations: Cloud computing • Abstract Resources • Focus on your needs, not on hardware specs. • On-demand Provisioning • Ask for what you need, exactly when you need it. • Large Scale • Cloud is conceptually of infinite capacity. • No Up-front Hardware Investment • Costs are in direct proportion to actual usage. • Cost-Effective & Efficient • No investment in depreciating hardware.

19. Cloud Considerations: Environmental Sustainability “Green IT has reached critical mass. Virtuallyall the companies we surveyed (97 percent) are discussing their Green strategy.” “Green IT Report Regional Data – United States and Canada: Survey Results,” Symantec, May 2009 “Enterprise PCs are wasting money. Far too many organizations leave economic and environmental value on the table by not reducing PC-related energy costs.” “How Much Money Are Your Idle PCs Wasting?,” Forrester Research, Inc., December 2008 “IT's role will increasingly be about applying the technology to create more-energy- efficient, less-carbon- intensive business models, enterprises, value chains, products and services with reduced environmental impact.” “User Survey Analysis: Sustainability and Green IT, Worldwide, 2009,” Gartner, Inc., April 2009 “Transformation in the way people and businesses use technology could reduce annual man-made global emissions by 15 per centby 2020 and deliver energy efficiency savings to global businesses of overEUR 500 billion[GBP 400 billion/USD 800 billion].” “SMART 2020: Enabling the Low Carbon Economy in the Information Age,” The Climate Group, June 2008

20. Cloud and Environmental Sustainability • Lower Carbon Emission due to • Multi tenancy • Quick Provisioning • Optimization of resources • Datacenter efficiency • Virtualization Enterprise can reduce the carbon emissions by 20 to 90 percentage by moving to cloud

21. When Is Cloud Computing Fit For The Enterprise? Applications & processes have highly variable demand High compute capacities are required to accelerate information discovery and publishing Time-constrained or event-based infrastructure is required to ramp quickly and be disposed of shortly afterwards Speed of provisioning is constraining business execution Existing hardware has reached end of serviceable life and refresh options are being considered Internal datacenter capacity limits are being reached and hosting locations must be re-balanced

22. Example: BPOS\Office 365 EA Approach • Reduce IT cost • By Integrating the IT Infra • Major IT investment area is Messaging and Collaboration • Cloud based messaging and Collaboration services. • On premise email service for the specific users need ITAR compliance • Overall will reduce the per user mailbox cost (savings of 27$ per user per month) Solution approach • Consolidated single unified directory structure • Central IT • BPOS Cloud based messaging and Collaboration Services • 27$ per user per month saving • Carbon Emission- 79% reduction for Exchange online, 90% reduction for SharePoint • Global company- Manufacturing • Acquired multiple companies • Business Challenges • No integrated IT, more than 5 separate companies not integrated • IT Cost is very high • Some of the infra is end of life cycle • Unused resources • No maturity of IT • Increasing end user needs • Different type of users – Users with high and demands • Branding • Compliance – ITAR for set of users

23. Hybrid Solution Online On-premises Overview

24. Cloud Impact- BPOS/ Office 365 REDUCED MANAGEMENT NEW ECONOMICS INCREASED PRODUCTIVITY • Pay for what you use • Lower and predictable costs • Shift from capex and opex • Accelerate speed to value • No patching, maintenance • Faster deployment • Robust multi-layered security • Reliability and fault-tolerance • Latest software for users • Internet collaboration • Anywhere access • Instant self-provisioning

25. Process Benefits What would it cost you to achieve…

26. Example: AWS • Major Retailer • Global Market reach • Has existing and future strategies using Web 2.0, social media, crowdsourcing collaboration etc as part of it marketing and reaching the younger generation • Have Facebook group of over 650,000 members EA Approach • Cloud based IaaS and Elastic Computing • Cloud Workshop to describe the art of the possible • Architect and Design future platform for Internet/Extranet deployments • Resilience, Scalability, expandable • Support and management • Secure • Solution AWS based Infrastructure as a service • Business Benefits • Speed : Rapid deployment cycle enabled immediate verification of application development, and launch timescales • Cost Reduction: • Agility : Can quickly adapt and change in line with instant business/artistic needs • Scalable: To meet needs of planned/unplanned peaks, and then back to normal volumes • Integrated : Into client’s existing monitoring and management environment, for minimal process impact • Extendible : To take further requirements and need and incorporate into the environment • Business Challenges • Fast changing market by its very nature • Expanding Digital Media strategies with accelerated plans for launch of more social and collaborative Web areas • Real need for speed of deployment and agility • Business groups already empowered to make own choices – IT has to keep up and support • Ambitious timescales for next launch – repeating cycle • Increasing costs of external agencies to host if not in IT Speed of deployment and agility are key

27. Solution Overview Solution • Load balanced Web/App based on Linux, Apache, Ruby-on-Rails (using AWS Elstic Load Balancing) • MySQL DB in HA configuration • Based on AWS core components • EC2 Compute, EBS storage, Load balancing, autoscaling • S3 Storage for holding Images • Use of 3rd party CDN for Image Content Distribution • 3rd Party software solution • CohesiveFT VPN Cubed for secure management and monitoring of AWS back to Client’s management console. VPN allowed extending the Burberry datacenter to the instances on AWS. • zManda Backups and recovery • Nagios monitoring • SubCloud – for mapping S3 as a drive on EC2 • Integration of Nagios Alerts into Client’s own Management console Extensible Architecture ready for future applications & requirements

28. Questions?

29. Thank YOU