Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>SQL Azure is the way to go if you're planning on sticking with an RDBMS (and you should be able to use any existing RDBMS repository implementation for this).</p> <p>However, if you want to use the more scalable <a href="http://msdn.microsoft.com/en-us/library/dd179423.aspx" rel="nofollow noreferrer">Table Storage</a>, then you might want to look into <a href="http://cloudstorageapi.codeplex.com/" rel="nofollow noreferrer">CloudStorage.API</a>, which provides a wrapper around this (it purports to aim for other cloud storage endpoints too, but AFAICT it's quite Azure specific). It will also enable better unit testing and dependency injection than the provided implementation in the Azure samples.</p> <p>You'll have a <a href="http://martinfowler.com/eaaCatalog/unitOfWork.html" rel="nofollow noreferrer">Unit Of Work</a> interface to work with with <a href="http://cloudstorageapi.codeplex.com/Wiki/View.aspx?title=Entities&amp;referringTitle=Home" rel="nofollow noreferrer">IEntityTableDataContext</a> and then creating your own <a href="http://martinfowler.com/eaaCatalog/repository.html" rel="nofollow noreferrer">Repository</a> implementation on top of this shouldn't require much effort.</p> <p>The main thing you'll need to be aware of is the restrictions that the <a href="http://msdn.microsoft.com/en-us/library/dd179423.aspx" rel="nofollow noreferrer">Table Storage</a> imposes on your entities - they basically need to be very simple property-exposing classes. For a richer domain model, you may want to explore mapping these data entities to your domain entities (you could use <a href="http://www.codeplex.com/AutoMapper" rel="nofollow noreferrer">AutoMapper</a> to assist you here too).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload