Database FAQs

Question 1

What is 'Database' and what problem does it solve?

Accepted Answer

'Database' offers pluggable MCP (Micro-Cloud Platform) servers for MySQL and PostgreSQL, built on a shared core. It simplifies direct data querying and management for both databases through independent server processes and a unified FastAPI gateway.

Question 2

Which database systems does 'Database' currently support?

Accepted Answer

'Database' provides dedicated, independent server processes, drivers, and prompts specifically for MySQL and PostgreSQL databases, allowing for robust and separated management.

Question 3

How does the caching feature work in 'Database'?

Accepted Answer

'Database' includes an optional TTL (Time-To-Live) cache. You can control caching globally via environment variables or on a per-call basis using `use_cache` and `ttl` parameters, optimizing data retrieval performance and reducing load.

Question 4

Can 'Database' be extended to support other database systems?

Accepted Answer

Yes, 'Database' is designed with an extensible architecture. Developers can easily add new database drivers, prompts, and server files to integrate and support additional database systems beyond MySQL and PostgreSQL.

Question 5

What is the purpose of the unified FastAPI gateway?

Accepted Answer

The unified FastAPI gateway in 'Database' serves both MySQL and PostgreSQL services under a single process. It provides a consistent API interface (e.g., `/mysql/*` and `/pgsql/*` routes) for easier integration into applications and streamlined management.

Database

About

Key Features

Use Cases