Unified Polyglot Persistence: Managing SQL and NoSQL with a Single API

In the landscape of modern application development, one size rarely fits all—especially when it comes to data storage. Your application might rely on a relational SQL database for transactional integrity, a NoSQL document store for flexible user profiles, and an in-memory cache for speed. This strategy, known as polyglot persistence, is powerful but introduces a significant challenge: operational complexity.

How do you manage, monitor, and scale this diverse collection of data resources without drowning in a sea of different dashboards, CLIs, and configuration files?

The answer lies in a paradigm shift: treating your services as software. It's time to stop juggling disparate tools and start managing your entire data estate as code through a single, powerful API.

The Challenge of a Multi-Database World

Using the best database for the job is a strategic advantage. However, the operational reality can be a heavy burden for DevOps and platform engineering teams. Common pain points include:

• Tool Sprawl: Every database type comes with its own management interface, query language, and operational tooling.
• Configuration Drift: Maintaining consistency for security policies, user access, and performance tuning across different databases and environments is a constant battle.
• Complex Workflows: Simple tasks like provisioning a new database for a staging environment or scaling a cluster become multi-step, error-prone processes.
• Lack of Visibility: Getting a unified view of all your data resources—their status, cost, and health—is nearly impossible without significant custom engineering effort.

This is where the concept of database as code becomes a game-changer.

Your Data, Managed as Code with databases.do

databases.do introduces an agentic workflow platform built on a simple yet profound idea: your data infrastructure should be as manageable and repeatable as your application code. It provides a unified abstraction layer over your entire collection of data resources.

Instead of manually configuring each database instance, you define your entire data estate in code. This allows you to:

• Provision new databases (SQL, NoSQL, Graph, etc.) with a simple function call.
• Query and manage resources across your entire project through a single API endpoint.
• Scale distributed databases consistently and reliably.

This "Services as Software" approach transforms complex data operations into simple, repeatable workflows that can be version-controlled, peer-reviewed, and automated.

A Single API to Rule Them All

The core of the databases.do platform is its unified API. It abstracts away the specific implementation details of each database, allowing you to perform high-level management operations on your entire collection of resources.

Consider a common task: getting a list of all active databases in your project. With databases.do, it's a single, straightforward API call.

import { databases } from '@do/sdk';

// List all databases within your project
async function listAllDatabases() {
  try {
    const allDbs = await databases.list();
    console.log('Available Databases:', allDbs);
    return allDbs;
  } catch (error) {
    console.error('Failed to retrieve databases:', error);
  }
}

listAllDatabases();

This code isn't talking to PostgreSQL, then MongoDB, then Redis. It's making one call to the databases agent, which understands your entire ecosystem. This same principle applies to scaling, configuring, and managing your resources, dramatically simplifying database management and enabling powerful automation.

Frequently Asked Questions (FAQs)

What is databases.do?

databases.do is an agentic workflow platform that allows you to manage collections of data resources as code. It provides a unified API to provision, query, and scale multiple databases, abstracting away the underlying infrastructure complexity.

How is this different from database.do?

database.do refers to a single data resource or instance. databases.do refers to the management of a collection of these resources, allowing you to perform operations across multiple databases at once, like listing all available databases or applying a configuration change to a group of them.

What types of databases can I manage?

The .do platform is designed to be extensible. You can manage various types of databases, including SQL, NoSQL, and graph databases, by integrating the appropriate drivers and defining them within your agentic workflows.

How do I get started with databases.do?

You can start by installing the .do SDK and authenticating your account. From there, you can use the databases agent to list existing data resources or define and provision new ones using simple code.

Embrace Unified Database Management

The era of polyglot persistence doesn't have to be an era of operational chaos. By embracing a database as code philosophy, you can bring the same rigor, automation, and scalability to your data layer that you expect from your application code.

With databases.do, you gain a single point of control and visibility, enabling your team to move faster and more reliably. Stop managing databases one by one and start orchestrating your entire fleet of data resources through a powerful, unified API.

Ready to transform your data operations? Explore databases.do and bring sanity to your polyglot persistence strategy today.