Sterling DB vs. Local Database in Mango

A few weeks back I had Jeremy Likness on Yet Another Podcast discussing Sterling,  his terrific SQL database that runs on top of Isolated Storage.  Recently we announced that Mango will have Local Storage (SQL CE) on top of Isolated Storage.  Does this make Sterling obsolete?  Absolutely Not

Jeremy, with his usual openness and calmness, explains how the products are differentiated, and the future of Starling in this brief blog post.  Among the points he makes are:

  • Sterling is dead simple
  • Sterling turns an object graph into bytes and back
  • With sterling you can share models between client and server
  • Classes can have behavior and Sterling will handle it.
  • Sterling supports Tombstone<t> without the need to convert to strings
  • Sterling is lightweight and flexible

Jeremy’s post is well worth reading in its entirety and I for one wish him the very best with this complimentary technology.

About Jesse Liberty

Jesse Liberty is a Senior Consultant with Wintellect, with three decades of experience writing and delivering software projects. He is the author of 2 dozen books and multiple Pluralsight & LinkedIn Learning courses, and has been a Senior Technical Evangelist for Microsoft, a Distinguished Software Engineer for AT&T, a VP for Information Services for Citibank and a Software Architect for PBS. He is a Xamarin Certified Mobile Developer and a Xamarin MVP and a Microsoft MVP.
This entry was posted in Essentials. Bookmark the permalink.

3 Responses to Sterling DB vs. Local Database in Mango

  1. Paulo says:

    I just want to say I am just newbie to bolgging and truly savored this blog site. Probably I’m planning to bookmark your website . You surely come with good article content. Kudos for sharing your website page.

  2. Curt says:

    “…Sterling, his terrific SQL database…”

    I do believe Jeremy refers to Sterling as *NoSQL.*

  3. Pingback: Sterling DB vs. Local Database in Mango | WP7 Developers Links

Leave a Reply

Your email address will not be published. Required fields are marked *