Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Azure storage tables as backend instead of CosmosDB #107

Open
jeevanions opened this issue Mar 31, 2023 · 2 comments
Open

Use Azure storage tables as backend instead of CosmosDB #107

jeevanions opened this issue Mar 31, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@jeevanions
Copy link

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.

@DCMattyG DCMattyG self-assigned this Mar 31, 2023
@DCMattyG
Copy link
Contributor

DCMattyG commented Mar 31, 2023

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.

@jeevanions
Copy link
Author

Fine. Thank you

@DCMattyG DCMattyG added the enhancement New feature or request label Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants