ITP 140 Mobile App Technologies. Web Hosting and Cloud by Nathan Greenfield

Transcription

1 ITP 140 Mobile App Technologies Web Hosting and Cloud by Nathan Greenfield

2 Today s overview 1. Introductions 2. Web hosting 3. Self hosted 4. The cloud 1. Software as a Service 2. Platform as a service 3. Infrastructure as a service 5. Case studies 6. My two cents 2

3 Nathan Greenfield Education BS in CS from UCSD MS in CS from USC Coding experience Ericsson SAIC Hilton Hotels IT Medical IT Medical Retail IT 3

4 Web hosting 4

5 Case study: WordPress hosting Domain registration ecommerce Unlimited storage Unlimited bandwidth No ads Live chat support Is that really worth $299? 5

6 Case study: Namecheap.com hosting Ultimate Shared hosting ($131.80/yr) Unlimited storage Unlimited bandwidth Database backend (MySQL, PostgreSQL, PHP admin) Server software (Apache, PHP, CGI, Perl, Javascript, SSI, Ruby on Rails, SSH Access, eacellerator, xcache Analytics, Scripting, 99.9% uptime 6

7 How do we get from this 7

8 to this? 8

9 What does a web host really give you? Physical resources Compute, storage, internet connection Software resources Hosting (web, database, OS), web libraries (PHP, Ruby on Rails, ASP) Human resources Hardware/software support, backups Icing on the cake , domain registration, management tools 9

10 Self hosted 10

11 Network connection Inbound Think download speed Home connection through TWC ~7GB/hr for $35/mo Needed to receive requests for page data Need static IP address Like: = Outbound Think upload speed Home connection through TWC ~0.5GB/hr for $35/mo Needed to send web browsers your web pages 1 view to = 0.31MB (for main page) If all 40k students and 24k faculty/staff viewed main page in 1 hour = about 19 GB in 1 hour 11

12 Network hardware Firewall Monitors and allows traffic flow across your network Load balancer Distributes traffic equally across all your servers (consider it a 1-to-many connection) Switch Allows all connected computers to communicate (consider it a many-to-many connection) Cabling Lots and lots of cables 12

13 Network diagram 13

14 Server hardware Web server Modest machine (~$3k) 32GB RAM per CPU, 1-2 CPUs, 300GB SSD for storage Database server IO bound machine (~$13k) 64+GB RAM per CPU, 2+ CPUs, 500+GB RAID SSD storage Application server Processing bound machine What does your app need? Network storage Big disk array (network attached storage) ($3k for 16TB) What does your app need? 14

15 Hardware infrastructure concerns Physical Ventilation, cooling, storage Power Clean power, backup power, power distribution Maintenance Repairs, replacements, upgrades Data Security, backup, growth 15

16 Let me introduce you to a server 16

17 Come up and look, servers don t bite 17

18 Software Free stack OS: Linux Server: Apache, Lighttpd, Nginx Database: MySQL*, PostgreSQL, MariaDB Paid stack OS: Linux (RedHat), Microsoft Server: IIS, vendor specific solution Database: Oracle, SQL Server, SAP Hana Application stack Backend: Wordpress, PHP, Java, Python, Ruby 18

19 Software stack concerns Support Who s maintaining your software? Could the product be abandoned? Compatibility Hardware concerns Software interoperability Customization How much customization is needed? Does only 1 person know how the whole thing works?! 19

20 Software infrastructure concerns OS security Virus, malware, intrusion Data security Backups, information hygiene Maintenance Updates, server-side software compatibility, browser compatibility, testing 20

21 The Cloud 21

22 The Cloud timeline 1997: Term cloud computing emerges 1998: VMware founded Allows virtual computers on host OS 1999: Salesforce founded Arguably the first SaaS product : Dot-Com bubble burst Incentivizes companies to cut costs by outsourcing 2005: 1 st CPU with virtualization support 22

23 The Cloud timeline 2002: AWS launches Arguably the first IaaS product 2007: Dropbox launches Cloud storage becomes a commodity 2008: US Fed announces cloud guidelines Vendors flock to comply 2012: GSA moves 17k users to Google Apps 2013: CIA signs AWS for private Gov-cloud 23

24 What is The Cloud? The Cloud is possible because of virtualization The abstraction of resources (compute, storage, etc.) No longer worry about individual servers or hard drives The Cloud usually refers to services available through the Internet 24

25 Vendor/User perspective on XaaS 25

26 Software as a Service 26

27 SaaS defined Software delivery model describes how software is provided and accessed by users Software is owned by provider Software is managed by provider Software is provided on a pay-for-use basis Sometimes on a subscription One common application services many users Traditional distribution: discrete copies are licensed 27

28 SaaS considerations Do you plan on providing SaaS? Will you allow access to the backend API? Is it a thin/rich client app? Mobile app? What about legal concerns? How do you keep clients data separate? Is there any proprietary data? Can you provide audit trails in case of a legal suit? Is there a Service Level Agreement? 28

29 Service Level Agreement (SLA) Not to be confused with the End User License Agreement (EULA) or Terms and Conditions for use Describes the services provided Describes the minimum uptime percentages Availability Downtime per month 90% ( one nine ) 3 days, 2 hours, 24 minutes 99% ( two nines ) 7 hours, 26 minutes, 36 seconds 99.9% ( three nines ) 44 minutes, 38 seconds 99.99% ( four nines ) 4 minutes, 27 seconds % ( five nines ) 26 seconds 29

30 Case study: Netflix (streaming) Originally founded in 1997 Streaming began (hosted by AWS) AWS outages effected Netflix service April 2011 June 2012 October 2012 Developed Simian Army to plan for outages Revenue: ~4.3B (2013) Operating expense: ~$3.3B (2013) 30

31 Platform as a Service 31

32 PaaS defined Sometimes called middleware 3 rd party (PaaS provider) provides and maintains foundational technology (hardware, server-side software, etc.) Can be the foundation to build a SaaS web app Allows SaaS provider to rely on PaaS provider for all but application software and data 32

33 What comes with PaaS? Software (all but yours) Server side environment Database system Hardware Compute resources Storage Network access Support Backups Maintenance And more! 33

34 Pros and cons of PaaS Pro: Fast startup allows you to focus on your web app Con: You pay a premium for the ability to focus on your web app Pro: You don t need a SysAdmin to manage your resources Con: You don t have a SysAdmin to maximize your usage of available resources 34

35 Case study: Heroku Founded in July 2007 out of YCombinator Based on AWS platform AWS outages effected Heroku service April 2011 June 2012 October 2012 Purchased by SalesForce in 2010 for $250M Customers include CareerBuilder, Asics, and LevelUp 35

36 Infrastructure as a Service 36

37 IaaS defined Sometimes called Hardware as a Service Hardware is owned by 3 rd party Software and data is managed by you Virtual hardware is managed by you Consequences of over/under provisioning Create your own redundancy/reliability plan IaaS provider has full access to all infrastructure Encrypt your resting data! 37

38 Pros and cons of PaaS Pro: Allows most control over cost and capacity Con: Requires maintenance and administration over virtual computers Pro: Allows more customization than PaaS Con: Requires more maintenance than PaaS Pro: Not required to maintain a server Con: Must rely on 3 rd party audits of hardware for validation and certification 38

39 Case Study 39

40 AWS product offering (incomplete) Compute Elastic compute cloud (EC2) Storage Simple Storage Service (S3) Glacier Elastic Block Store (EBS) Database DynamoDB Relational Database Service (RDS) ElastiCache Networking & Content Delivery Route 53 CloudFront 40

41 AWS product offering (incomplete) Analytics Elastic Map Reduce (EMR) Kinesis Redshift Application Services Elastic Transcoder (ETS) Flexible Payment Service (FPS) Deploy & Manage CloudWatch Elastic Beanstalk CloudFormation Support Trusted Advisor 41

42 Lets build an application! Microsoft SharePoint External facing website Internal facing website Content management Document management Business intelligence Collaboration And more! 42

43 SharePoint solution Create an web server EC2 instance 43

44 SharePoint solution Connect it with a SharePoint server on EC2 44

45 SharePoint solution Connect the application with a DB instance 45

46 SharePoint solution Sandbox the servers for protection 46

47 SharePoint solution Create redundant instances for high-availability 47

48 SharePoint solution Balance load among application servers 48

49 SharePoint solution Setup transition between private and public networks (public subnet) with load balancer Allows distinction between intranet users and internet users 49

50 SharePoint solution What if there s an outage? 50

51 SharePoint solution Connect it to the Internet (and balance the load between the two zones) 51

52 and the grand total? Around $1750/month Supports 500 concurrent users Requires NO software licenses AWS rolls software into monthly cost Have option to use your existing licenses Works out to $3.5/month per user No capital expense to run system Need more capacity? Add more instances! For estimated expense see saved calculator 52

53 Case study

54 Condé Nast web hosting needs Availability Highly accessible, unrestricted by traffic demands Redundancy Minimum downtime and transparent failover Security Segregation of services Segregation of data (public and private) Development environment Ability to thoroughly test changes before rollout 54

55 Condé Nast digital Germany Source: GoGrid case study analysis 55

56 My two cents 56

57 Let me should on you Start with PaaS Allows focus on web app with minimal labor Research the companies look for market leaders Transition to IaaS with growth When you can afford the overhead of monitoring a virtual server farm Avoid running your own hardware Canned hybrid/private cloud solutions exist and will be the next round products 57