thanks a lot!!!
the problem is as our buddies said:
If I do everything into one database, that will result on scale into a terrible performance. or not? because dgraph doesn’t know that I e.g: want social media stuff into one alpha node and ecommerce stuff into the other alpha node. dgraph will just balance them randomly based on the disk usage. that means that everything will be mixed up. then my joins have to cross abroad to multiple alpha nodes(=machines), that will create a terrible latency. or not?
it would be really awesome to have different big projects in one single world wide dgraph database, that would allow awesome query capabilities. but if dgraph won’t shard stuff logically(recognize which data is used frequently together to shard between services like socialmedia and ecommerce), but instead based on disk usage which will result in a mix that leads to terrible performance latency and so on. or not?