Most products assume a Relational Database under the hood. The other models have not been as popular. The reason is that it is being used as an “Integration Database Model”.
With the scaling issues of Relational Databases, the “Application Database Model” is becoming popular. With this model
- HTTP/ REST / WebServices is used as the primary vehicle of Integration
- Each application is free to choose the Database that best serves its application needs.
Simpler Database Schema
With breaking the iron-tight requirement of “Database Integration”, it becomes easier to split the database into smaller functional components, the data model becomes simpler to maintain
Easier Schema and Product Evolution
Each of the individual components can evolve better through “Evolutionary Schema Design and Refactoring”.