Chapter title: Software as a Service and Cloud Computing
This page turns Chapter 9 into a cleaner study guide focused on how firms shift computing from owned systems to services delivered over the Internet. The big ideas are virtualization, containers, SaaS, PaaS, IaaS, public/private/hybrid cloud, AWS, serverless computing, cloudbursting, scalability, vendor lock-in, latency, TCO, and the strategic winners and losers created by cloud adoption.
Chapter 9 explains how firms replace owned hardware and software with computing services delivered over the Internet. The chapter is not only about “using the cloud.” It is about who manages each layer of the tech stack, how cost structure changes, what risks move to vendors, and how cloud services change competition, entrepreneurship, and IT jobs.
| Term | Precise definition | Why it matters in MIS | Citation |
|---|---|---|---|
| Virtualization | Virtualization is software that lets one computer or cluster function as if it were several different computers, each with its own operating system and software. | It boosts hardware utilization, lowers cost, and underpins much of cloud computing. | Course slides, p. 9; textbook Ch. 9 |
| Virtual machine | A virtual machine is a software-based representation of a physical computer, complete with an operating system and installed software. | It allows firms to move, copy, scale, and manage computing more flexibly. | Textbook Ch. 9 |
| Containers | Containers are a lighter form of virtualization that isolate applications while sharing an operating system. | They use fewer resources and start faster than traditional virtual machines. | Textbook Ch. 9 |
| Docker | Docker is a widely used open source technology for containerization. | It is a major part of modern cloud software deployment. | Textbook Ch. 9 |
| Kubernetes | Kubernetes is software used to coordinate and manage multiple containers across computing resources. | It helps large-scale container environments remain organized, scalable, and resilient. | Textbook Ch. 9 |
| Virtual desktop | A virtual desktop is a remotely served PC environment where the OS, apps, and files run on a server and are displayed to a user device. | It simplifies security, updates, support, and large-scale PC management. | Textbook Ch. 9 |
| Cloud computing | Cloud computing means replacing local hardware or software with computing services delivered over the Internet. | It changes cost structure, staffing needs, speed, and competitive dynamics. | Course slides, pp. 7, 10, 16; textbook Ch. 9 |
| SaaS | Software as a service (SaaS) is software delivered online by a third party, usually through a browser or app. | It requires the least internal support because the vendor manages almost everything. | Course slides, pp. 9, 13, 16, 21; textbook Ch. 9 |
| PaaS | Platform as a service (PaaS) provides a cloud-based platform with tools for building, testing, and deploying applications. | It is useful when a firm wants to write its own software without managing all infrastructure details. | Course slides, p. 9; textbook Ch. 9 |
| IaaS | Infrastructure as a service (IaaS) provides computing, storage, and networking resources over the Internet. | It gives firms the most control, but also the most setup and maintenance responsibility. | Course slides, p. 9; textbook Ch. 9 |
| Service model | A service model describes how much software and hardware responsibility the cloud vendor handles versus the customer. | Choosing SaaS, PaaS, or IaaS is a core managerial cloud decision. | Textbook Ch. 9 |
| Public cloud | A public cloud relies on a third-party provider to run the information system on shared infrastructure. | It can offer scale and lower cost but increases vendor dependence. | Textbook Ch. 9 |
| Private cloud | A private cloud is a pool of computing resources owned or leased by one organization and not shared with others. | It can offer control and compliance advantages, but with more internal cost and responsibility. | Textbook Ch. 9 |
| Hybrid cloud | A hybrid cloud combines internal resources with public cloud resources. | It lets firms keep some workloads in-house while shifting overflow or selected projects to the cloud. | Textbook Ch. 9 |
| Cloudbursting | Cloudbursting is the use of cloud resources to provide overflow capacity during spikes in demand. | It helps firms avoid overbuilding internal systems for rare peak usage. | Textbook Ch. 9 |
| SLA | A service level agreement (SLA) is a negotiated agreement that specifies performance, availability, serviceability, or uptime commitments. | It is important because cloud customers depend heavily on vendor reliability. | Textbook Ch. 9 |
| Latency | Latency is delay in sending and receiving data across a network. | Cloud and SaaS can feel slower than local systems when many network hops are involved. | Course slides, pp. 21, 24, 25; textbook Ch. 9 |
| TCO | Total cost of ownership (TCO) is the full cost of a system, including purchase, deployment, training, support, and change over time. | Cloud may lower upfront cost but still needs full financial analysis over time. | Course slides, pp. 17–18; textbook Ch. 9 |
| Vendor lock-in | Vendor lock-in is dependence on one provider that makes switching difficult or costly. | It is a major risk in SaaS and cloud adoption. | Textbook Ch. 9 |
| Consumerization of technology | Consumerization of technology refers to employees adopting outside digital tools on their own, often without IT oversight. | Cloud and SaaS make it easier for unauthorized or inconsistent tools to spread inside firms. | Textbook Ch. 9 |
| AWS | Amazon Web Services (AWS) is Amazon’s category-leading cloud platform offering compute, storage, databases, AI, and many other services. | It is one of the most important examples of cloud scale, early-mover advantage, and platform leadership. | Textbook Ch. 9 |
| EC2 | Elastic Compute Cloud (EC2) is AWS’s service for launching virtual servers in the cloud. | It gives firms flexible computing but still requires configuration and maintenance choices. | Textbook Ch. 9 |
| Lambda | Lambda is AWS’s service for running cloud functions without the developer managing servers directly. | It is an example of serverless computing that increases speed and reduces infrastructure work. | Textbook Ch. 9 |
| Serverless computing | Serverless computing lets developers write code that runs in the cloud without directly managing servers, operating systems, or much of the surrounding infrastructure. | It shifts even more technical burden from the customer to the cloud vendor. | Textbook Ch. 9 |
| S3 | Simple Storage Service (S3) is AWS’s scalable cloud storage service. | It acts like a nearly limitless cloud hard drive and supports many kinds of systems. | Textbook Ch. 9 |
| Redshift | Redshift is AWS’s managed data warehouse service for large-scale analytics. | It helps firms turn cloud-stored data into decisions and insight. | Textbook Ch. 9 |
| Instance | An instance is a software-based copy created from a predefined model, such as a virtual server or desktop. | Managers will hear about spinning up instances as firms allocate cloud resources on demand. | Textbook Ch. 9 |
| Availability zone | An availability zone is a distinct cloud infrastructure location within a geographic region used for redundancy and fault tolerance. | It helps cloud vendors provide uptime, speed, and disaster recovery. | Textbook Ch. 9 |
1) Virtualization is one of the most important hidden technologies in business computing. Chapter 9 starts here because virtualization is what makes a lot of cloud economics possible. If one physical server can behave like many machines, firms do not need to waste money buying separate hardware for every application. That means higher utilization, lower cost, and more flexibility.
2) Containers push efficiency even further. Traditional virtual machines carry their own operating systems, which uses more resources. Containers isolate applications but share the OS, so they are lighter and faster. That is why Docker and Kubernetes matter in modern deployment, even if students do not need the deep engineering details.
3) Cloud computing is really about outsourcing parts of the tech stack. The slides make this especially clear. In SaaS, the vendor manages almost everything. In PaaS, the vendor manages most of the stack while the client builds its own application. In IaaS, the vendor mainly provides hardware-like resources and the client does much more of the rest.
4) The most useful managerial question is not “Should we use cloud?” but “Which parts belong where?” Many firms should not move every system into the cloud. Some workloads fit SaaS. Some require the flexibility of IaaS. Some firms keep sensitive or regulated systems in private or hybrid environments. So cloud is a design and governance decision, not a one-word answer.
5) SaaS changes software from a capital purchase into an operating expense. Instead of buying hardware, licenses, and support up front, firms often pay monthly or by usage. That can reduce financial risk, improve flexibility, and make sophisticated systems available to smaller firms. But it also creates ongoing dependence on the provider.
6) Cloud is powerful because it handles scale that firms would otherwise overbuild for. A company with only occasional traffic spikes does not want to buy enough hardware for the rare peak and let it sit mostly idle. Cloudbursting and elastic cloud resources solve that problem by turning rare peak demand into variable spending rather than fixed capacity.
7) The main benefits of cloud are cost, speed, expertise, and flexibility. Large cloud vendors are better at backup, recovery, fault tolerance, infrastructure security, and global scaling than most firms can be on their own. This means internal staff can spend less time keeping systems running and more time on strategic work.
8) The risks of cloud are dependence, outages, legal exposure, and mismatch with unique processes. Chapter 9 repeatedly warns that cloud is not a silver bullet. If a vendor fails, changes its product, goes down, or does not fit a firm’s unique requirements, the customer can be in real trouble. This is especially true for mission-critical systems.
9) Latency is a real business issue, not just a technical one. The slides even use online Excel as a practical example. When files and computing bounce across multiple remote systems, delays and mistakes can happen. That matters for user experience, productivity, and even assignment submission in everyday settings.
10) Cloud has changed competition across the tech industry. It weakens some traditional hardware and packaged software markets while strengthening services, infrastructure platforms, and firms with massive data center scale. It also lowers barriers to entry, which helps startups do more with less capital.
11) AWS is not just a product example; it is a strategy example. AWS shows how an early mover can build customer lock-in, platform complements, internal learning, and major scale advantages. The chapter uses AWS to show that cloud leadership is both a technology story and a competitive strategy story.
| Model | What the vendor handles | What the customer handles |
|---|---|---|
| SaaS | Software, hardware, updates, backups, and most support | Mostly user-side use and limited configuration |
| PaaS | Hardware, operating system, development platform, testing, hosting | Application creation and deployment |
| IaaS | Hardware, storage, networking, core infrastructure | Operating systems, apps, databases, and much of configuration |
| Model | What it means | Best fit |
|---|---|---|
| Public cloud | Third party runs the system on shared infrastructure | Scale, speed, and lower upfront cost |
| Private cloud | Organization owns or leases the cloud resources for its own use | Control, compliance, and large-scale internal needs |
| Hybrid cloud | Mix of internal resources and public cloud resources | Flexible balancing of control and scalability |
| Category | Traditional virtualization | Containers |
|---|---|---|
| Isolation unit | Virtual machine | Application container |
| Operating system | Each VM usually has its own OS | Containers share an OS |
| Resource use | Heavier | Lighter |
| Speed | Slower to start | Faster to start and run |
| Typical tools | VMware and other hypervisor tools | Docker + Kubernetes |
| Benefit | Why it matters | Chapter 9 takeaway |
|---|---|---|
| Lower upfront cost | No huge hardware, software, and setup purchase | Turns large fixed investment into variable spending |
| Faster deployment | Firms can start quickly without building everything | Speeds experimentation and rollout |
| Scalability | Capacity can expand during spikes | Prevents overbuying for rare peak demand |
| Vendor expertise | Cloud leaders know backup, recovery, security, and large-scale operations | Internal staff can focus on strategic work |
| Remote access | Systems can be reached from many devices and locations | Supports distributed work and mobile use |
| Potentially greener computing | Large cloud vendors pool and cool systems more efficiently | Can reduce waste and energy use |
| Risk | Why it happens | Manager implication |
|---|---|---|
| Vendor dependence | Critical systems and data are tied to one provider | Need strong partner selection and contingency planning |
| Outages | If the provider fails, the client may fail too | Mission-critical systems need redundancy planning |
| Forced change | Vendors may roll out new versions or interfaces | Can create training and process disruption |
| Latency | Data travels across networks instead of staying local | User experience and productivity may suffer |
| Security and legal concerns | Data is stored off-site and may cross jurisdictions | Compliance review and security governance remain essential |
| Limited flexibility | Some SaaS tools do not match unique business processes | Not every workload should move to cloud or SaaS |
| Service | What it does | Why it matters |
|---|---|---|
| EC2 | Creates virtual servers in the cloud | Flexible but needs more setup and maintenance |
| Lambda | Runs functions in the cloud without direct server management | Faster development and less infrastructure burden |
| Workspaces | Provides remotely served virtual desktop computers | Useful for secure, standardized desktop environments |
| S3 | Stores large amounts of cloud data | Acts like a nearly limitless hard drive |
| Redshift | Supports cloud-based data warehousing and analytics | Turns stored data into decision support |
A fast-growing startup originally bought separate servers for each internal application. A new IT manager shows that most of those servers are barely being used, yet the firm still pays for hardware, floor space, cooling, and maintenance. She recommends consolidating workloads so multiple isolated environments can run on the same physical machines. The founders want to know which concept best explains the savings.
Which concept BEST fits the manager’s recommendation?
A retailer wants to build a custom internal application for store scheduling and inventory alerts. The firm does not want to manage physical servers or database patching, but it does want its own developers to write the application logic. One executive suggests buying a finished SaaS product instead. Another suggests using a cloud provider mainly for infrastructure and then configuring everything else themselves.
Which service model is the BEST fit for the retailer’s stated needs?
A university system keeps its core student records on internal infrastructure because of policy and compliance concerns. But during registration week, traffic spikes so sharply that internal systems slow down. The IT group proposes keeping normal operations in-house while shifting extra demand to a public cloud provider only when spikes happen.
Which option BEST describes this strategy?
A small company adopts a cloud-based analytics platform because the monthly price looks much lower than buying servers and licenses. Six months later, managers realize they did not fully account for implementation work, training, workflow changes, support, and the cost of storing data they rarely use. The CFO now says the company focused too much on sticker price and not enough on the full economic picture.
Which concept BEST explains the CFO’s complaint?
A student uses online Excel while the file itself is stored remotely on Box, then tries to upload the file to another online system. The upload fails, and the professor explains that the problem comes from the fact that the work, the file, and the destination all live in different places connected over networks. The student assumed “cloud” meant everything would feel as direct as working from a local laptop file.
What is the BEST explanation of the problem?