Software as a Service (SaaS), Service-Oriented Architecture (SOA), and Cloud Computing Extracted and modified from Engineering Software as a Service slides by David Patterson and Armando Fox 1
High-Level Overview 2
What Makes a Great Software Engineer? P. Li, A. Ko, J. Zhu, Microsoft & Univ. of Washington, Proc. ICSE 2015 59 interviews with recognized SE experts at Microsoft Always improving Passionate Technically open-minded Data-driven Personal Characteristics Decision Making Knows people & organization Updates mental models when learn new skills/facts/context Consider situation at multiple levels when making judgments Can reason about complex & intertwining ideas Helps others understand by tailoring explanations to them Creates shared success possibly via personal compromises Creates safe haven where others can learn from mistakes Gives honest feedback Team Skills Technical Skills Elegant solutions Creative thinking when faced with limitations of current solutions Anticipates technical needs based on prior experience 3
Which aspect of the software lifecycle consumes the most resources? (A) (B) (C) (D) Design Development Testing/debugging Maintenance 4
Shrink-wrapped software client-specific binary, frequent upgrades Must work w/many versions of HW, OS, Libraries, Hard to maintain Extensive compatibility testing per release Alternative: server app, client=browser Search, email, commerce, social nets, video Now also productivity (Google Docs/Office 365), finance (TurboTax Online), IDEs (Codenvy) 5
1990s-2000s: SaaS > SWS 1. No install worries 2. Data stored safely in cloud 3. Groups can share/collaborate on data 4. 1 copy of SW, single HW/OS environment no compatibility hassles for developers beta test new features on 1% of user simplifies upgrades for developers no user upgrade requests 5. Continuous customer feedback possible, respond by rolling out new changes quickly 6
Smartphone Native Apps: Back to the future? + Use HW features unavailable in HTML5 + May be faster or not Many just HTML5 apps in native container + Your brand is on user s home screen Though can get this with bookmarks too Harder to maintain Upgrades now once again user s problem Alternative: HTML5+JS, eg Framework7 7
Service-Oriented Architecture 8
Bookstore: Silo Internal subsystems can share data directly Review access user profile All subsystems inside single API ( Bookstore ) 9
Bookstore: SOA Subsystems independent, as if in separate datacenters Review Service access User Service API Can recombine to make new service ( Favorite Books ) 10
Software Architecture Can you design software so that you can recombine independent modules to offer many different apps without a lot of programming? [Amazon CEO Jeff Bezos] realized long before the vast majority of Amazonians that Amazon needs to be a platform. Steve Yegge, Googler, former Amazonian, in a 2011 blog post 11
2002: Amazon shall use SOA! 1. All teams will henceforth expose their data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no sharedmemory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. 12
CEO: Amazon shall use SOA! 4. It doesn't matter what [API protocol] technology you use. 5. Service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. 6. Anyone who doesn't do this will be fired. 7. Thank you, have a nice day! 13
Which of the following is a disadvantage of SOA compared to a silo design? A B C D SOA may be harder to debug & tune SOA results in lower developer productivity SOA s complexity is a poor match for small teams SOA is more expensive to deploy than Silo, because more hardware is needed to handle the same workload 14
Cloud Computing 15
What is ideal HW for SaaS? Amazon, Google, Microsoft developed early hardware systems to run SaaS What did they use: Mainframes? Supercomputers? How can independent SW developers build SaaS apps and compete without similar HW investments to Amazon, Google, Microsoft? 16
Ideal hardware infrastructure for SaaS? SaaS s 3 demands on infrastructure 1. Communication Allow customers to interact with service 2. Scalability Fluctuations in demand during + new services to add users rapidly 3. Dependability Service & communication available 24x7 17
Services on Clusters Clusters: Commodity computers connected by commodity Ethernet switches 1. More scalable than conventional servers 2. Much cheaper than conventional servers 20X for equivalent vs. largest servers 3. Dependability via extensive redundancy 4. Few operators for 1000s servers Careful selection of identical HW/SW Virtual Machine Monitors and containerization (Docker, Kubernetes) simplify operations 18
Warehouse Scale Computers Clusters grew from 1000 servers to 100,000 based on customer demand for SaaS apps Economies of scale pushed down cost of largest datacenter by factors 3X to 8X Purchase, house, operate 100K v. 1K computers Traditional datacenters utilized 10% - 20% Earn $ offering pay-as-you-go use at less than customer s costs for as many computers as customer needs 19
2007: Utility Computing arrives Buy computing, storage, communication by the hour (from $0.04/server/hour) 1000 computers @ 1 hour = 1 computer @ 1000 hours FarmVille on AWS Prior biggest online game had ~5M users 4 days =1M; 2 months = 10M; 9 months = 75M Amazon EC2, Google Cloud, Microsoft Azure Individual developers now have access to same computing power as heavyweights 20
Which statement about private datacenters vs. public utility computing (such as AWS) is true? (A) (B) (C) (D) Private datacenters are not shared by multiple companies/competitors Private datacenters may be the only option for some highly-regulated apps Private datacenters are inherently more secure than public utility computing Private datacenters could match the cost of public utility computing if they just used the same type of hardware and software 21
In Summary SaaS less hassle for developers and users SOA makes it easy to reuse current code to create new apps Scale led to savings/cpu, reduced cloud computing cost, and utility computing 22