You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current infrastructure can be made simple, and cost-effective and use Azure services for DR purposes. Is there a way that we can make Azure Storage Tables the backend for this application? CosmosDB is an expensive option.
Maybe make the backend API like an interface and we can have different Databases to plugin to depending upon the requirement of the user.
The text was updated successfully, but these errors were encountered:
Hey there @jeevanions, this may be a more challenging ask. Everything is written around using the Cosmos SQL API, and we rely on Cosmos specific items, such as ETAG to avoid conflicts (such as 2 IPAM users making a similar change simultaneously).
There are ways to control the Cosmos costs by limiting RU's on the database/container, and making sure Autoscale is properly configured.
Perhaps sometime in the future I can look further into this, but for now there are far too many dependencies on Cosmos DB.
The current infrastructure can be made simple, and cost-effective and use Azure services for DR purposes. Is there a way that we can make Azure Storage Tables the backend for this application? CosmosDB is an expensive option.
Maybe make the backend API like an interface and we can have different Databases to plugin to depending upon the requirement of the user.
The text was updated successfully, but these errors were encountered: