design-scalardb

Designing distributed transactions across heterogeneous storages requires a cluster topology that coordinates multi-storage environments. This Skill generates a ScalarDB Cluster architecture defining storage backends, transaction strategies, and cross-service transaction schemas.

Coordinating PostgreSQL, DynamoDB, and Cassandra in a single microservice data platform is possible by defining storage mappings and transaction strategies. The design workflow outputs a cluster topology mapping these heterogeneous backends for cross-service transactions.

Planning a migration from a legacy database to an HTAP-ready schema involves stepwise migration roadmaps. This Skill provides phased migration plans alongside namespace definitions and table schemas to transition multi-storage environments.

Defining cluster topology and storage backends for a multi-storage environment requires architectural specifications for transaction strategies and storage mapping. The workflow enforces these specifications to generate a ScalarDB cluster design document.

ScalarDB Cluster supports HTAP-ready schemas for distributed transaction processing by enforcing namespace and table definitions. It applies to projects needing distributed transactions across heterogeneous storages with specific transaction guarantees.

A ScalarDB Cluster architecture for microservices should not be used when your project lacks requirements for distributed transactions across heterogeneous storages or HTAP-ready schemas, as the design enforces specific topology and storage mapping specifications.