Are there any best practices for using dgraph in a microservices architecture? Usually in microservices arch, you would not have two different services talking to the same datastore (Shared Databases in Microservices Are a Problem - DZone Microservices / Database per service). This is because you’d typically want to be able to launch, scale and monitor each service separately and databases inherently become single points of failure, and queries can become noisy neighbours to other queries.
What’s the best practice for Dgraph if multiple microservices want to talk to it? I assume you’d want to have a set of dgraph instances right, rather than having a shared DB across things?