Neo4j Database Modeling with respect to microservice architecture

If we are using microservice architecture with one neo4j instance per microservice, how does neo4j benefits this architecture with respect to other microservices? And how should one break the neo4j models into different microservices?

Assume we have to build a twitter clone referencing this awesome post by MAX DE MARZI. Following is the database model we would have if it would be a monolithic app.

2X_8_8caae04969b4553cbe02cd11067bf19e46cdb646.png

Suppose if we have 2 microservice named as M1 - which is for User management in all the informations regarding a particular user is stored and then we have a M2 microservice in which all the tweets, chats, retweets, etc. are stored. How should we model the database to support this architecture?

Hi David,

rescuing this reply to see the state of Neo4j in relation to microservices architecture nowadays. In our project we started with a monolithic approach and now we are considering moving to a microservices architecture.
Also, I don't see much content on this topic (Microservices + 1 (or more) Neo4j instances)

Thank you.