“Mobilize” your existing SQL Azure tables (from WASD to ZUMO)

I have been playing around with Windows Azure Mobile Services (ZUMO) and found a great article on Using an existing Azure SQL table with Windows Azure Mobile Services by Jeff Sanders. I have been trying to do the same but found some challenges along the way.

If you are using EF Data Migrations on you project you will need to ensure the schema is set to the name of the Mobile Service name instead of dbo (this might be tricky for some); or use the EF DB First Model approach. In addition to that you will need to make sure the column types being used by your app are compatible with the types for ZUMO. Lastly remember to set the id (Not ID as it is case sensitive) column to be an identity column.

With those small changes you will be able to access your previously created tables via ZUMO while minimizing impact to any legacy webapp you may have developed earlier.

Hope this helps :-)

Additional References:

Moving an Access DB to Windows Azure Mobile Services by Scott Klein

Creating a EF DB First Model with SQL Azure by Julie Lerman

Using existing database with Azure Mobile Services by Filip Woj

Do you or do you not know about the VERB… Cause everybody’s heard that the VERB is the word

Like Peter Griffin said the bird is the word, I say the VERB is the word. What I’m I talking about? HTTP Verbs.

I have been recently playing with Windows Azure Mobile Services commonly called ZUMO. In doing so I ran into a bit of a snag. I was trying to do CRUD operations from an MVC 4 app when i kept getting an error on updates. As many people know the typical mapping for REST APIs is something like this:

Read: HTTP GET
Insert: HTTP POST
Update: HTTP PUT
Delete: HTTP DELETE

While I had no issues inserting or reading the update action was failing with the following error “{“MethodNotAllowed“}. After some digging I was able to spot the issue. The ZUMO REST API is expecting the PATCH Verb instead of PUT.

I replaced the following:

var request = new HttpRequestMessage(HttpMethod.Post, BaseAddress);

with

HttpClient client = new HttpClient();
client.DefaultRequestHeaders.Add("X-ZUMO-APPLICATION", ApplicationKey);
client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
var request = new HttpRequestMessage(new HttpMethod("PATCH"), BaseAddress + contact.id);

That little tweak did the trick!

Hope this helps others playing with Windows Azure Mobile Services too. If you haven’t go ahead and give it a try :-)

Cloud adoption: It's not about the price, stupid

Reblogged from GigaOM:

Click to visit the original post

Don't look now, but there has been a shift in thinking around why companies move -- or should move -- workloads to the cloud. A few years ago, most of the talk was all around saving money. Look at how cheap Amazon(s amzn) Web Services are! Pennies per hour to spin up instances! We don't need to buy more servers!

Read more… 449 more words

It has always been about scaling resources quickly not minimizing dollars. But a good scaling down strategy WILL save money also. The problem is that the same thing we do in our On-Premise servers we do in our Cloud instances... we over-spin.

CloudCheckr Raises $2M To Help AWS Customers Analyze Resources, Costs And Security

Reblogged from TechCrunch:

Click to visit the original post
  • Click to visit the original post

Cutting through Amazon Web Services complexity is becoming quite a business. CloudCheckr is the latest to leverage AWS' lack of tools for analyzing resources, costs and security with the news of a $2 million investment and the general availability of its freemium service. The Series A round was led by Garrison Capital with Genesee Capital also participating.

Here's how it works.

Read more… 501 more words

More and more we see monitoring as the key pillars in lowering OpEx for cloud.

Mejorando mi App con Windows Azure Mobile Services!

Reblogged from MSEstudiantes Tech:

Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post
  • Click to visit the original post

En este post: exploraremos la aplicación inicial de WAMS, la mejoraremos con scripts desde el servidor, y le agregaremos identificación con Microsoft Account por medio del Live SDK! 

Es hora de mejorar las aplicaciones de Windows 8, y que mejor que hacerlo con Windows Azure Mobile Services! ;)

Es por ello que si se han perdido la introducción que he realizado sobre Windows Azure Mobile Services (WAMS) es mejor que lo vean:

Read more… 815 more words