Chapter 6

Chapter 6 generalizes the concept of solid database structures and how to implement them. Normalization is the first key topic that stands out to me here. Any developer working on a project should have a clear scope of how to handle each task at hand. Normalization is the key to this. Developers tasked with planning out what is necessary to make a project work must then normalize the tasks at hand to remove redundancy from the project.

Other points this chapter focus on include security and integrity, The former focuses on safe keeping databases from malicious actors through blocking unauthorized access of user accounts or data stored in the database. Users should only have access to the data pertinent to their account and the intended function of the app being used. The concept of integrity then goes on to focus on the fact that data in a database should be stored as it was intended to be. There should be checks put in place so that data does not become miss managed or corrupted from wrongful access. For example, gracefully handing two users editing the same page twice. Google docs is excellent at this and will show each user what is currently being edited to all other connected users. While GitHub for example can only allow one user to edit a given page at a time to prevent any previously written data being lost.

In summation, to ensure responsible database handling programmers should employ solid database security and integrity methods to produce a quality product.

Leave a comment

Design a site like this with WordPress.com
Get started