Micro Services Architecture

[median meteor]

Hi! I'm developing my first application with microservices and I have a doubt.

I'm using relational database, how would I do with the information when I have a many to many relationship?

Because I have read that for each microservice there must be a database (go segmenting the database).
For example, in the microservice "companies", I should have a database that hosts the companies that exist.
And for the microservice "accounts", there should be a database with the accounts.

The problem arises in:
What if I have a many-to-many relationship between accounts and companies? What database would the pivot table be in?

[willow mist]

Perfect example of why microservices are a bad idea.

Why on earth would you split them out?

[median meteor]

Scalability, availability and the ability to have more than one development stack

Example

[willow mist]

Why on earth

This doesn't make sense unless you're working in some enterprise scale company that has heaps of legacy code and hundreds of developers.

Best of luck with it but makes no sense to me

[wintry lintel]

@median meteor This is clearly a case where microservices isn’t the answer.