Learning Objectives

By the end of this chapter, you will be able to:

  • Define what a Cloud Database is.
  • Understand the Database-as-a-Service (DBaaS) model.
  • Compare cloud databases with on-premises databases.
  • Identify the advantages and risks of using cloud databases for modern businesses.

What is a Cloud Database?

A Cloud Database is a database that typically runs on a cloud computing platform (like Amazon Web Services, Microsoft Azure, or Google Cloud) rather than on local on-premises servers. It provides the same functionality as a traditional database but with the added flexibility of cloud computing.

Users and applications reach a cloud database over the internet, so staff in different branches, or customers using a mobile app, all work with the same live data.

Deployment Models

There are two primary ways businesses use cloud databases:

  1. Virtual Machine (VM) Deployment: The organization rents a virtual server in the cloud and installs their own database software on it. The organization is responsible for maintenance, updates, and backups.
  2. Database-as-a-Service (DBaaS): The cloud provider manages the database software, hardware, backups, and scaling automatically. The organization simply uses the database without worrying about the underlying infrastructure.
    • Examples: Amazon RDS, Google Cloud SQL, MongoDB Atlas.
flowchart TB
  ORG[Organization Apps] --> CLOUD[Cloud Platform]
  subgraph CLOUD
    VM[VM Deployment: you manage DB software]
    DBaaS[DBaaS: provider manages DB]
  end
  VM --> DATA[(Cloud Database)]
  DBaaS --> DATA
  DATA --> REP[Replication and Backups]

Figure 1: Cloud Database Deployment Models

Types of Cloud Databases

  • Relational (SQL) cloud databases store data in tables with fixed structure; suited to accounting, banking, and inventory. Examples: Amazon RDS for MySQL/PostgreSQL, Azure SQL Database, Google Cloud SQL.
  • NoSQL cloud databases store flexible documents, key–value pairs, or graphs; suited to fast-changing app data, product catalogues, and chat. Examples: MongoDB Atlas, Amazon DynamoDB, Google Firestore.

Cloud vs On-Premises Databases

Aspect On-premises database Cloud database
Location Servers in the organization’s own building Servers in the provider’s data centers
Upfront cost High: buy servers, storage, licences Low: pay monthly for what you use
Scaling Slow: buy and install new hardware Fast: add capacity in minutes
Maintenance In-house IT team patches and backs up Provider handles much of it (especially DBaaS)
Access Mainly from the office network From anywhere with internet access
Control Full control over hardware and data location Less control; depends on provider and contract
Internet reliance Works on the local network without internet Needs a reliable internet connection

Advantages of Cloud Databases

  • Cost Efficiency: No need to purchase expensive hardware or pay for unused capacity. You pay only for the storage and compute power you use.
  • Scalability: Resources can be automatically scaled up during peak traffic and scaled down when quiet, ensuring consistent performance.
  • High Availability & Disaster Recovery: Cloud providers automatically replicate data across multiple geographic locations, ensuring the database stays online even if a data center fails.
  • Reduced IT Burden: DBaaS handles routine tasks like software patching and backups, allowing IT teams to focus on business logic rather than maintenance.

Risks and Challenges

  • Internet dependence: if the office internet link fails, staff may lose access to the data.
  • Security and privacy: sensitive customer data is stored with a third party, so encryption and strict access control are essential.
  • Vendor lock-in: moving a large database from one provider to another can be difficult and expensive.
  • Data location and regulation: some regulators require certain data, such as financial or government records, to be stored within the country.
  • Ongoing costs: monthly bills can grow quickly if usage is not monitored.

Business Scenario

An online clothing store in Kathmandu expects ten times its usual traffic during the Dashain–Tihar sale. With an on-premises server, it would have to buy hardware that sits idle for the rest of the year. With a cloud database, it scales capacity up for the festival weeks and back down afterwards, paying only for the extra capacity it actually used. Automatic backups also protect its order data if a server fails.

In Nepal, government agencies host many systems at the Government Integrated Data Center (GIDC), while startups and many private firms use global cloud providers or local data-center and cloud services.

Summary

Cloud databases represent a massive shift in enterprise architecture. By moving data storage to the cloud, organizations gain unparalleled scalability, cost flexibility, and reliability compared to traditional on-premises solutions. They must, however, manage internet dependence, security, vendor lock-in, and data-location rules.

Key Takeaways

  • A cloud database runs on a cloud platform and is accessed over the internet.
  • Businesses use either a self-managed VM or a provider-managed DBaaS.
  • Cloud databases can be relational (SQL) or NoSQL.
  • Benefits: low upfront cost, fast scaling, high availability, and less maintenance.
  • Risks: internet dependence, security, vendor lock-in, and regulation of where data is stored.

Review Questions

  1. What is a cloud database? How does it differ from an on-premises database?
  2. Explain DBaaS with two examples.
  3. Why might a bank hesitate to move its core database to a foreign cloud provider?
  4. Discuss the advantages and risks of cloud databases for a growing e-commerce business in Nepal.