Overview

IBM Db2 as a Service is a family of data management products, including database servers, developed by IBM. It supports various data models and types, including structured (like JSON and XML) and unstructured data.

IBM Db2 SaaS delivers a fully managed, cloud-native deployment of the Db2 database engine, optimized for transactional and analytical workloads. Integrated with IBM Cloud security and monitoring services, it supports high availability, automated backups, point-in-time recovery, and seamless scaling. The service is offered in multiple plans:

  • Lite Plan: free tier for development and testing, with limited storage and connections.
  • Standard Plan: suitable for production workloads, offering configurable compute and storage, encryption at rest, and automated patching.
  • Enterprise Plan: designed for mission-critical applications, with advanced HA/DR options, dedicated hardware, and enhanced performance SLAs.
  • Performance Plan: built on IBM Cloud virtual private cloud (VPC) Gen 3 infrastructure, this plan offers a dedicated instance on VPC machines with flexible scaling of compute, storage, and IOPS. The base configuration starts at 4v CPU x 16 GB RAM x 50 GB Storage

IBM Db2 SaaS comes with built-in high availability and disaster recovery capabilities, helping ensure continuous data access and protection against outages or data loss. These features are seamlessly integrated, allowing businesses to maintain uptime and resiliency without the complexity of manual configuration. The technology includes both synchronous and asynchronous replication modes to help ensure reliability and uptime within a single region. If a failure occurs, automatic client reroute (ACR) seamlessly redirects traffic to the standby high availability node, minimizing disruption. These high availability configurations are deployed within a multizone region (MZR) or single-zone region (SZR), depending on the plan.

With the geo-replicated disaster recovery nodes, you can now extend availability across regions. With this optional feature, you can create disaster recovery nodes in a separate geographic location, helping ensure continued access to data even if the primary region experiences an outage. For example, a primary instance that is hosted in Dallas can be paired with a disaster recovery node in London, providing cross-regional resiliency.