Separate queue provider and storage

What would it take / look like to separate queues out from storage? I've wished to see what it would take to split out queue providers from storage as they quite intertwined right now.

For example I would like to use Azure Table Storage with Azure Queue Provider, but looking at interfaces the storage would need to deal with interacting with the queues instead of being focused on purely data storage + retrieval.

The issue names no files, tests, or entry points. Start by tracing the storage and queue-provider interfaces and their interactions, then assess how Azure Table Storage and Azure Queue Provider would be composed independently. Done would require an agreed separation design and corresponding implementation scope.

Written by the indexing model from the issue text.