Triggers in a .NET NoSQL Database

By Basit Anwer

We know for a fact that one of the greatest things about a NoSQL database is the complete flexibility it provides developers. You do not have to pre-define anything in a collection; neither the columns nor the data-types.

This sounds awesome, but some fear the power of so much flexibility. And rightly so, if your NoSQL database is being accessed by different types of applications. In this case, it is possible that the data being entered does not follow any set of rules to ensure data format consistency, increasing the possibility of human errors just waiting to happen.

You’ve heard the phrase "with great power comes great responsibility." With a NoSQL database, I’ve talked with developers who do not want great data power, rather they want tools to reduce, or at least to corral, the infinite flexibility of their data so they are not responsible for every possible data combination. What I mean is that even though the data is unstructured and flexible, methods to exert some control over the data format are welcomed.