Skip to content
Blake Technologies

Data

Operational storage

Relational modeling with PostgreSQL, MySQL, or SQL Server; document storage where appropriate; object storage for files; Redis for caching. Choose consistency and recovery behavior to match the workload.

Discuss your project

Different information needs different storage behavior

Relational data

Business records

Transactions, relationships, and constraints.

Object storage

Files and evidence

Retention, access, and links to the owning record.

Cache

Disposable acceleration

Expiry, invalidation, and a reliable source behind it.

Choose storage around the record’s lifetime and correctness requirements. A cache should not become the accidental system of record, and a file should not lose its ownership or retention rules because it lives outside the database.

Recovery is a data requirement

Questions for each storage layer
RequirementDecision to record
Acceptable data lossHow recent must a recovered copy be?
Restoration timeHow quickly must the workflow resume?
RetentionWhen can records and backups be removed?
AccessWho may read, change, export, or delete the data?
How do we know a backup is useful?

Restore it in a controlled environment and verify the application can use the recovered records and files together. A successful backup job is not evidence of a complete restoration.

Your project, scoped around the outcome

Build with Operational storage

A data model, storage configuration, and a backup and restore plan.

Talk through the scope

Related technologies

All technologies