Greetings from Silicon Valley!
I’m a technology entrepreneur and (go, python, ruby) developer using dgraph in a project to help people get back to work post pandemic.
Being new to graphs, I’m trying to figure out the role of a SQL store in support of our graph for our specific use case. It seems like the right idea but I’m so hard wired to SQL I’m unsure. 
As I start to wrap my head around this concept:
- We should keep a dgraph UUID in our entity tables with a unique index.
- Anything else on each graph entity? Type?
I welcome your inputs and advice on this SQL/graph hybrid architecture. 
Speaking of SQL, I’ll be doing a very non-trivial SQL migration and will post questions, findings, etc, elsewhere in these forums.
Super glad to be a new part of this great community!
Regards,
John Knapp