14 - Cloud and Local Databases — Module Topics

Introduction to Database Deployment Models

Overview of the two primary database deployment approaches: locally hosted systems and cloud-based services. Establishes foundational concepts and context for comparing the two models.

What Is a Database Deployment Model? — A database deployment model refers to the environment and infrastructure strategy used to host, manage, and access a database system.
Locally Hosted Database Systems — A locally hosted database, often called an on-premises database, runs on physical hardware owned and managed by the organization itself.
Cloud-Based Database Services — Cloud-based database services deliver database functionality over the internet through third-party providers, eliminating the need for organizations to manage underlying hardware.
Key Dimensions for Comparing the Two Models — When evaluating locally hosted versus cloud-based databases, several core dimensions help frame the comparison objectively.
Why the Choice of Deployment Model Matters — Selecting the right deployment model is a foundational architectural decision that influences an organization's agility, security posture, and long-term operational costs.

Locally Hosted Database Systems

Examination of on-premises database infrastructure, including setup, management responsibilities, and common use cases. Covers the characteristics that define local deployment environments.

Definition and Core Characteristics of Local Deployment — A locally hosted database system is one that runs on physical hardware owned and operated by the organization itself, typically within its own data center or server room.
Infrastructure Setup and Configuration — Standing up a locally hosted database requires procuring, assembling, and configuring physical hardware before any database software can be installed.
Management Responsibilities — In a local deployment model, the organization assumes full responsibility for every layer of the database stack, from hardware maintenance to software patching.
Cost Structure of On-Premises Databases — Locally hosted databases involve significant upfront capital expenditure (CapEx) for hardware and licensing, along with ongoing operational costs.
Scalability Considerations — Scaling a locally hosted database is constrained by physical hardware limits and procurement timelines, making it less flexible than cloud alternatives.
Common Use Cases for Local Database Deployment — Despite the rise of cloud services, certain organizational needs and constraints make locally hosted databases the preferred or required choice.
Availability and Disaster Recovery Challenges — Ensuring high availability and disaster recovery for locally hosted databases requires deliberate design and significant additional investment in redundant infrastructure.

Cloud-Based Database Services

Introduction to major cloud database platforms including AWS RDS, Azure SQL, and Google Cloud SQL. Explores how these managed services operate and what features they offer.

What Are Managed Cloud Database Services? — Managed cloud database services are fully hosted database solutions provided by cloud vendors, where the provider handles infrastructure, maintenance, and availability.
AWS RDS (Relational Database Service) — Amazon Web Services offers RDS as a managed relational database service supporting multiple database engines in a scalable cloud environment.
Azure SQL Database — Microsoft Azure SQL Database is a fully managed relational database service built on the SQL Server engine and optimized for the Azure cloud platform.
Google Cloud SQL — Google Cloud SQL is a fully managed relational database service on Google Cloud Platform, supporting MySQL, PostgreSQL, and SQL Server.
Core Features Common to Cloud Database Platforms — Despite differences in vendor ecosystems, major cloud database services share a consistent set of features designed to reduce operational burden and ensure reliability.
Connectivity and Access to Cloud Databases — Cloud database services are accessed remotely via secure connection endpoints, requiring configuration of network rules and authentication credentials.

Cost Comparison: Cloud vs. Local

Analysis of the financial trade-offs between cloud and local database deployments, including capital expenditure versus operational expenditure models. Covers licensing, hardware, and ongoing service costs.

Capital Expenditure vs. Operational Expenditure — Local database deployments typically follow a capital expenditure (CapEx) model, requiring large upfront investments, while cloud deployments shift costs to an operational expenditure (OpEx) model with ongoing subscription or usage-based payments.
Hardware Costs in Local Deployments — Running a local database requires purchasing and maintaining physical hardware, including servers, storage systems, and networking equipment, all of which represent significant upfront and recurring costs.
Licensing Costs: On-Premises vs. Cloud — Database software licensing represents a major cost component that differs significantly between local and cloud deployments, with cloud providers often bundling licensing into service pricing or offering managed alternatives.
Ongoing Operational and Maintenance Costs — Beyond initial setup, both local and cloud database deployments incur ongoing costs, though the nature and visibility of these costs differ substantially between the two models.
Scalability and Cost Efficiency — Cloud databases offer the ability to scale resources up or down based on demand, which can improve cost efficiency compared to local deployments that must provision for peak capacity at all times.
Total Cost of Ownership (TCO) Analysis — A complete financial comparison between cloud and local databases requires a total cost of ownership (TCO) analysis that accounts for all direct and indirect costs over a defined time horizon.

Scalability and Performance

Comparison of how cloud and local databases handle growing data demands and performance requirements. Highlights the scalability advantages and limitations of each deployment model.

Elastic Scalability in Cloud Databases — Cloud databases such as AWS RDS, Azure SQL, and Google Cloud SQL offer elastic scalability, allowing resources to be scaled up or down dynamically based on workload demands.
Scalability Constraints of Local Databases — Local or on-premises databases are limited in scalability by the physical hardware available, requiring capital investment and lead time to expand capacity.
Performance Optimization in Cloud Environments — Cloud database services provide built-in performance tools such as managed caching, automated query optimization, and globally distributed nodes to meet demanding performance requirements.
Performance Characteristics of Local Databases — Local databases can deliver predictable, high performance for specific workloads when hardware is properly configured and dedicated exclusively to database operations.
Handling Growing Data Demands — As data volumes grow, the deployment model significantly influences how easily and cost-effectively a database system can accommodate increased storage and throughput needs.
Trade-offs Between Scalability and Cost — While cloud databases offer superior scalability flexibility, the ongoing operational costs of scaling can exceed the capital costs of on-premises infrastructure for certain workloads.

Maintenance and Administration

Evaluation of the administrative burden associated with each deployment model, including patching, backups, and monitoring responsibilities. Contrasts self-managed maintenance with provider-managed services.

Self-Managed Maintenance in Local Deployments — When hosting a database locally, the organization assumes full responsibility for all maintenance tasks, including software updates, patching, and hardware upkeep.
Provider-Managed Maintenance in Cloud Deployments — Cloud database services such as AWS RDS, Azure SQL, and Google Cloud SQL offload most routine maintenance responsibilities to the cloud provider.
Backup and Recovery Responsibilities — Backup strategies differ significantly between local and cloud deployments, affecting both the administrative effort required and the reliability of recovery options.
Monitoring and Performance Management — Ongoing monitoring of database health, performance, and resource utilization is a critical administrative task that differs in effort and tooling between deployment models.
Administrative Staffing and Expertise Requirements — The choice between local and cloud-managed databases has direct implications for the type and volume of database administration expertise an organization must maintain.
Shared Responsibility Model — Cloud database deployments operate under a shared responsibility model, where the provider and customer each own distinct maintenance and security obligations.

Availability, Reliability, and Security

Examination of uptime guarantees, disaster recovery options, and security considerations for both deployment models. Discusses how each approach addresses data protection and business continuity.

Uptime Guarantees and SLAs — Cloud database providers typically offer formal Service Level Agreements (SLAs) that guarantee a specific percentage of uptime, often 99.9% or higher.
Disaster Recovery in Cloud Deployments — Cloud database services provide built-in disaster recovery features, including automated backups, geo-redundant storage, and point-in-time restore capabilities.
Disaster Recovery in Local Deployments — Local database deployments require organizations to design and maintain their own disaster recovery strategies, which can be resource-intensive.
Data Security in Cloud Databases — Cloud database providers implement extensive security measures, including encryption at rest and in transit, identity and access management, and compliance certifications.
Data Security in Local Deployments — Local database deployments give organizations full control over their security posture but place the entire responsibility for protection on internal teams.
Business Continuity Considerations — Business continuity planning ensures that database services remain available or can be rapidly restored during disruptions, and each deployment model offers different strengths in this area.