Split API into micro-services
<p>I've have one question about architecture.</p>

<p>We have api for mobile backed. And now we implementing some new features, like <strong>user messaging</strong>. 
For no api uses one database, and I want to have separate api and database for messages. Like micro-services. api.somedomain.com, messages.somedomain.com, etc. </p>

<p>Main api is guarded by implementing access via access keys. And in micro-services databases I need some data from main database, like user info, profile info, etc. </p>

<p>Maybe someone have ideas how to implement such mechanism? </p>

<p>Maybe master-slave replication with slave = database where I need information from main database? </p>