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

Document DB is too expensive #14

michael-mansour opened this issue Jul 4, 2017 · 1 comment


None yet
2 participants
Copy link

commented Jul 4, 2017

Hi, my parse App haves 5-6 classes. Azure translate each class as a collection on Document DB. The problem is that having so many collection (5 approximately) is very expensive (+250$/month). Do you have a less expensive approach? My App is relatively small and I can't afford to pay 300$ per month. (I’ve a budget of 100€/month)
Thank you very much


This comment has been minimized.

Copy link

commented Jan 5, 2019

We’re having the same problem. If this can’t/won’t be solve within this library, do you know any tips we can follow to try to keep the number of entities to a minimum? We’re starting to be scared every time we need to add a new entity...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.