The other day I was chatting with my colleague Nick Pinheiro about possible architectures of mobile solutions with Azure. As you may or may not know Windows Azure is the Microsoft Cloud. They provide a bevy of services from Website hosting to API creation, data storage, machine learning and much more. Nick and I are in the process of building separate mobile applications and we often spit-ball ideas about the architecture of our applications and how we handle certain scenarios as they come up with our applications. to set the basis of what we have been discussing, Nick’s application started off as a web application (actually, it’s a Facebook app in which Nick was honored as having one of the top Facebook apps on the planet!). He is now in the process of making his app a native mobile application. My application comes from the perspective of building a brand new Azure Mobile Services application. Both approaches have their own unique pros and cons. So this lead us to wonder what might be the pros and cons of using Windows Azure Mobile Services vs. building a mobile application using the individual (A la Carte) services offered by Windows Azure. So that is what we will be discussing in this post.