Most data anti-patterns are schema design-and application-focused and so are out of the scope of this book. By identifying bottlenecks in data persistence, retrieval, and storage, we find anti-patterns that can be addressed programmatically. We encourage you to review processes within your organization to break out of consequences related to Conway's law (as a quick reminder: systems mirror the communication structures of the organization that designed them).
It is imperative that you try to remain flexible in your solutions—try to use the right tool for the job. In some cases, it's not all that clear cut which tool is the right one as there may be several options; this is where experimentation comes in.
The design of the system should maximize the portability of your data. One way is by adhering to established standards and reducing the amount of vendor lock-in that you have in your system. This will ensure that new technologies can be...