When it comes to choosing the right technology for a new project, ongoing development or a full system upgrade, it can often be challenging to define the exact right tools that will match set-up criteria from start to finish. Especially, when it comes to choosing the right database. It has been actively discussed and debated by many experts that “one size does not always fit all”. This idea suggests that one would use different data models for different parts of large software architectures. Meaning that one has to use multiple databases in the same project, potentially resulting in some operational friction, data consistency and duplication issues. This is where a native multi-model database with all its benefits and flexibility comes into play.
In this white paper we explain what a multi-model database is, and why and where it makes sense to use it, including a use case based on aircraft fleet management.