Course contentsShow
← Cloud and Infrastructure
Lesson 399 of 2,9898. Managed DatabasesFree lesson

Database Instance Classes

Understanding instance types, CPU/memory configurations, and how to select appropriate instance sizes for workloads.

Database Instance Classes

What you'll learn: You'll discover how to choose the right compute power and memory for your managed database, just like picking the right engine for a car.


What Are Instance Classes?

In managed database services like AWS RDS, Azure Database, or GCP Cloud SQL, an instance class defines the CPU, memory, and network capacity allocated to your database server. Think of it like choosing between a compact car, a sedan, or a truck—each has different power and capacity for different jobs.

Instance classes determine:

  • CPU cores: Processing power for queries and transactions
  • Memory (RAM): Space for caching data and active connections
  • Network performance: Speed of data transfer to applications

Common Instance Class Patterns

Most cloud providers organize instances into families:

  • General Purpose: Balanced CPU and memory (e.g., db.t3.medium, db.m5.large)
  • Memory Optimized: Extra RAM for caching-heavy workloads (e.g., db.r5.xlarge)
  • Burstable Performance: Lower baseline with occasional burst capacity for dev/test (e.g., db.t3.small)

The naming typically includes size indicators like small, medium, large, xlarge, 2xlarge, etc., where each step up roughly doubles resources and cost.

Selecting the Right Size

Match your instance class to your workload:

  • Development/testing: Start with burstable or small general-purpose instances
  • Production with moderate traffic: General-purpose medium or large
  • High query complexity or large datasets: Memory-optimized instances
  • High transaction volume: Larger CPU counts with sufficient memory

You can monitor CPU utilization, memory usage, and connection counts to right-size over time. Most providers allow resizing instances with minimal downtime.


Key Takeaway: Database instance classes define your database's compute and memory resources—choose based on workload requirements, and remember you can resize as needs change.