Run VividEcho on Azure Cosmos DB or Google Firestore — same API surface, same behavior, different backing store. The database you sit on becomes a deployment decision rather than something baked into how you use the API.
VividEcho's platform architecture writes through a common persistence path so either Cosmos DB or Firestore can sit behind it, depending on the deployment target — Cosmos DB when running on Azure, Firestore when running on Google Cloud Platform. Application state is persisted to whichever store backs that deployment, without changing how the API behaves from the outside.
That means the choice of database is a platform deployment concern, not something your application code needs to account for — you interact with the same collections, verbs, and query syntax regardless of which store is running underneath.