title: Is using a database wrapper microservice an anti-pattern?
body: <p>Say I have a microservice that wraps a database, in a way that the entire functionality of that service is hiding the details of the database behind a generic (say REST) API, allowing changing the database without affecting the other services.</p>
  
  <p>Is this an anti-pattern? 
  What are the pros/cons of this approach?</p>