Chapter 4. What DBAs Want
DBAs maintain data in an RDBMS-centric information processing environment, and the typical DBA manages 40 databases containing an average of 5 TB of data.1 Therefore, many have developed a comprehensive, if somewhat protective, view toward maintaining data integrity and accessibility. Perhaps as a consequence, there is some concern in the industry that DBAs are now becoming a limiting factor as organizations attempt to speed up their delivery pipeline.2
ACID Compliance
To ensure streams of data are accurate and consistent, ACID compliance might be a requirement placed on our database management system. To that end, let’s review the ACID acronym:
- Atomicity
-
Make all changes or none.
- Consistency
-
All changes obey database rules.
- Isolation
-
Apply all changes step by step before showing any changes.
- Durability
-
Changes will be permanent.
Note: Some systems will claim “ACID” but ACID across one document is not the same as ACID across the dataset. Likewise, eventual consistency is not the same as formal consistency.
The choice of DBMS will determine whether the database can be trusted to provide the necessary reliability, or whether the developer will need to account for this in the application code.
Minimal Schema Changes
For DBAs, schema changes are critical transactions that need planning and careful execution. Frequent and reckless changes in schemas are both difficult to manage in RDBMSs and propagate risk in ways that are sometimes difficult ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access