Geek Answers Handbook

Azure differences between local structure and cloud data type processing

We recently debugged an Azure application after trying to move storage from local storage to cloud storage — the first step in moving the entire object to the cloud.

We ran into a problem where the local data store allowed us to store incorrectly initialized DateTime objects (initialized by DateTime.MinValue or "0") in the Azure storage table, but the cloud storage would give a "value out of range" when the value was committed to the table.

Is there a way for local storage to throw the same exceptions as the cloud?

Otherwise, is there a list of these things? I found an MSDN page about some of the differences , but there was nothing like it.

+4
source share
2 answers

Impossible make local storage and fabric the same as manufacturers. There are completely different implementations.

The practice we adopted at Lokad based on our experience with Azure:

  • start using production storage and fabric as early as possible in prototyping and development;
  • if you really need to, create design abstractions and helper classes that hide or handle critical differences or sharp edges of Azure.

Some of these abstractions and classes are available in open source projects for Azure:

+1
source

I think this is the page you want: http://msdn.microsoft.com/en-us/library/dd320275.aspx (The mismatch you saw is mentioned here.)

0
source

More articles:


All Articles