scalardb-data-model

To design a ScalarDB data model that avoids hotspots, you must structure partition keys to distribute transactional workloads evenly. This skill generates table schemas with hotspot risk assessments to ensure balanced access patterns across microservices.

Choosing ScalarDB partition keys and clustering keys requires aligning them with your specific data access patterns. This skill provides deterministic PK and CK designs with rationale to meet transactional workload constraints while minimizing metadata overhead.

You should use a secondary index in ScalarDB when query patterns require lookups outside the partition key, but you must evaluate metadata overhead. This skill estimates overhead to inform your secondary index decisions and back-end DB selection.

Selecting a back-end database for ScalarDB depends on your access patterns and scalability requirements. This skill provides guidance on choosing the appropriate underlying database based on workload analysis and hotspot risk evaluation.

Yes, you can generate ScalarDB table schemas for multiple microservices by providing your service domains and target databases. The skill outputs ready-to-apply schemas and design templates tailored to each microservice's data access patterns.