title: Service Fabric Actors - save state to database
body: <p>I'm working on a sample Service Fabric project, where I have to maintain a shopping list. For this I have a ShoppingList actor, which is identifiable by a specific id. It stores the current list content in its state using StateManager. All works fine.</p>
  
  <p>However, in parallel I'd like to maintain the shopping list content in a sql database. In particular:</p>
  
  <ul>
  <li>store all add/remove item request for future analysis (ML)</li>
  <li>on first actor initialization load list content from db (e.g. after cluster has been re-created)</li>
  </ul>
  
  <p>What is the best approach to achieve that? Create a custom StateProvider (how? can't find examples)? 
  Or maybe have another service/actor for handling all db operations (possibly using queues and reminders)?</p>
  
  <p>All examples seem to completely rely on default StateManager, with no data persistence to external storage, so I'm not sure what's the best practice.</p>