Seeking the Agile Path through Database Design
Being first to market or meeting rapidly changing customer demands compels development teams to build systems while requirements are still being discovered. Developing a relational database design ahead of its requirements can paint you into a corner—with a product that suffers from legacy-like limitations. Jonathan Wiggs shares ideas to solve this problem in an agile way that provides both support for the present and flexibility for the unknown future. When a database design is trying to meet too many requirements, you can tie its architecture to product concepts and get answers to questions such as one database or many? Learn to balance design flexibility with operational requirements including understanding the role of disk storage and physical implementation across various technologies from the desktop to the cloud. Jonathan covers specifics including the proper use of minor entity tables, denormalization, and elastic scaling mechanisms. Join Jonathan to see how your data architecture can lead innovation rather than drag behind as an obstacle to success.