Multiple Microservices readers/writers using the same Database table (Asking for Trouble??)
<p>Warning this is an open ended question but I am curious about peoples opinions on multiple Microservices reading from the same table in a database.  </p>

<p>I am currently working on a set of API's that exhibit a Microservice architecture but various endpoints need to read from the same table and there are a few background processes writing to the very same table.  This sounds like a bad architectural decision to me because no application team seems to own the schema due to multiple writers, if they want to make changes to it, then multiple code bases need to be updated. </p>

<p>My knowledge is fluffy on Microservices but this design decision sounds like an abuse of the Microservice architecture.</p>