I often hear the argument that one should only use the standard or in the cloud, the (OpenSource) tool specific features to be able to move anywhere else anytime.
No use of AWS specifics which would make developers live easier but doesn’t exist in Azure. SQL Standard instead of effective new datatypes or procedures that are vendor specific.
My favorite quote of the article:
> „Data has gravity“. Moving data can be both time-consuming and costly.
If you need to scale-out, the ArangoDB packages are more affordable then MongoDB Atlas, as you don't need to spin-up a whole 3 node replica-set to add another shard to your cluster. The smaller instances are cheaper in Atlas, here you benefit from the established cloud service, which can negotiate better conditions with the large cloud providers. However, we will pass on lower cloud costs to customers, so there is hope that we will move closer over time. But, I don't see ArangoDB in direct competition with smaller, pure document-use cases. Most users need the multi-model capabilities and use graphs in combination with document operations.
What I miss in the conclusion: Multi-model databases
More and more products support multiple data models today.
This reduces the number of technologies in your tech stack and allows to combine different access patterns without the need to duplicate and sync data between systems.
Is anyone already implementing such a service?