Document DB is too expensive

felixrieseberg / parse-server-azure

Adapters, tools, and documentation to use Parse-Server with Microsoft Azure

MIT License

23 stars 4 forks source link

Document DB is too expensive #14

Open michael-mansour opened 7 years ago

michael-mansour commented 7 years ago

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

dani-mp commented 5 years ago

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...