Over the life of an application, as requirements change, application usage patterns alter, load and performance changes, and monolith applications may get broken into microservices. The need to change database and database architecture is inevitable and may include architectural refactoring, structural refactoring, data quality refactoring, referential integrity refactoring, and database code refactoring. Pramod Sadalage discusses evolutionary database design, database refactoring patterns, and different implementation techniques to enable blue-green deployments, allow for legacy applications to work with fast changing database, and enable teams to effectively refactor the database to fulfill the changing needs of the organization.
Pramod dives into 10 patterns, for each, explaining how to apply changes, version control the changes, migrate the data, and integrate with the rest of the team and their changes.
The patterns include:
Pramod Sadalage is a director at ThoughtWorks, where he enjoys the rare role of bridging the divide between database professionals and application developers. Pramod is usually sent in to clients with particularly challenging data needs that require new technologies and techniques. In the early ’00s he developed techniques to allow relational databases to be designed in an evolutionary manner based on version-controlled schema migrations. Pramod is the coauthor of Refactoring Databases and NoSQL Distilled and the author of Recipes for Continuous Database Integration, and he often speaks and writes about the insights he and his clients learn.
Comments on this page are now closed.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com