Database & Schema
A database keeps organized data over time. Its schema says which entities, fields, types, and relationships are allowed.
Another example
An orders table links to customers and limits the allowed currency, amount, and status values.
Main parts
- 01Identity or input
- 02Policy or transformation
- 03Stored result and audit evidence
Use it when
Use a schema to keep facts true and explain what the data means.
Do not use it when
Never put every kind of data into one JSON field with no checks.
Name used in code
SQL / ORM schema Before you ship
Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.
Outcome: Design or review Database & Schema for this system while keeping data correct, secure, and easy to operate. User context: An orders table links to customers and limits the allowed currency, amount, and status values. Technical concept or control: Database & Schema. Why it fits: Use a schema to keep facts true and explain what the data means. Do not use it when: Never put every kind of data into one JSON field with no checks. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.
Check this request
Review the current use of Database & Schema. Definition: A database keeps organized data over time. Its schema says which entities, fields, types, and relationships are allowed. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.