So, you have database changes—either schema or data changes—that need to be implemented and rolled out across various environments. One approach could be to connect directly to each database server and execute scripts. However, you might not—and indeed, probably should not—have direct read/write access to certain environments like beta or production. Additionally, consider if a client posed the following questions; would you be able to easily respond? What is the state of the database in our Production environment?

Overview On my latest project, I had the opportunity to explore an alternative to relational databases: Document Databases. Document Databases belong to a category called NoSQL databases. I found a couple of advantages of using a document database compared to a traditional relational database, which I will demonstrate with an examples below. Schema flexibility Let’s say you have a table that stores user’s information. Let’s store just first and last name.