I would like to build task system (kind of github). I want to organize my data as following: organization -> project -> task This is a multi-tenant application (each node should be able to handle requests from multiple tenants).

I was thinking of using separate DB for each project. But the problem is that I need global “users” collection - the user should be able to participate in different organizations and projects accordingly. So probably it should be one parse application. As soon as service will be shared it probably makes sense to store all projects not in one collection by put each project into the separate collection which will help with sharing and scaling.

What are the potential problems of this kind of approach? Any recommendations?

Thank you in advance!

  • The last people who tried this ran out of money and shut down... – Michael Hampton Mar 5 '17 at 20:57
  • Could you please elaborate? I'm sure that each architecture has some limits... What the limit (or boatneck) in this approach? – DioNNiS Mar 5 '17 at 21:01
  • parse.com? I'm sure you heard of them. – Michael Hampton Mar 5 '17 at 21:02
  • I'm not sure that ran out of money was a real reason... it's another subject for discussion.. =) – DioNNiS Mar 5 '17 at 21:05

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.