0

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!

Dennis Liger
  • 101
  • 3

0 Answers0