You need to put the data in one database if you need access to it at the same time, as opposed to switching back in forth between multiple databases.
You just need to model your data, which means identify your node types (which correlate to entities) and the relationships between nodes. Next identify the properties you want to store in each node and relationship.
Myself, I don’t think in terms of graphs. I just think the database contains a collection of entities with relationships. You could have a collection of related nodes that don’t relate to another collection of related nodes. That is fine as long as they are part of a model needed for your application. Each application you may build would be contained in separate databases.
Finally create and analyze the data.
We can help with queries once your explain data and the outcomes you want to achieve.
Welcome aboard.
GraphAcademy has classes of data modeling and cypher. Take a look.
