Pune microsoft azure developers 2nd meetup

Editor's Notes

1. I will discuss following four topics in the next 30 minutes How azure helped the Halo 4 team to become successful using cloud technologies. The technologies and concepts which are becoming more relevant and of more concern given cloud technologies and their cost in place. How the cloud technology is changing the eco system around the IT engineering. Last , we will compare different models (Paas , Saas and Iaas) .
2. Basically, it’s a simple way to generate and host services that can be used in combination with mobile applications (not only Microsoft made, as we’ll see later) for different purposes: generic data services, authentication or push notification.   It isn’t something new: these services are built on top of the existing Azure infrastructure (the service is hosted by a Web Role and data is stored on a SQL Database), they’re just simpler for the developer to create and to interact with.   These services are simply REST services, that returns JSON responses and that can be consumed by any application.   Windows Azure Mobile Services makes it incredibly easy to connect a scalable cloud backend to your client and mobile applications.  It allows you to easily store structured data in the cloud that can span both devices and users, integrate it with user authentication, as well as send out updates to clients via push notifications.  
3. Shared backed with client SDKs for all mobile platforms. : still have to write different app , but the backend is same and exposed over REST . iOS, Android, Windows, Windows Phone, or HTML app, as well as use cross-platform frameworks such as Xamarin, Sencha, and PhoneGap. Client SDKs for each of these platforms making it easy to connect applications to the cloud-hosted backend. or each of these platforms making it easy to connect applications to the cloud-hosted backend. Easily incorporate authentication with Facebook, Twitter, Google , Microsoft . Easy integration with Apple Messaging System (AMS) Google messaging System (GMS) ,Windows Notification System(WNS) ,Microsoft Phone Notification System(MPNS)
4. The authentication endpoint for an Azure Mobile Service responds to GET requests to https://<service-name>.azure-mobile.net/login/<providerName>, where <providerName> is one of the supported authentication providers (currently “facebook”, “google”, “microsoftaccount” or “twitter”). When a browser (or the embedded browser control) sends a request to that address, the Azure Mobile Service runtime will respond with a redirect (HTTP 302) response to the appropriate page on the authentication provider (for example, the twitter page shown in the first image of this post). Once the user enters valid credentials, the provider will redirect it back to the Azure Mobile Service runtime with its specific authentication token. At that time, the runtime will validate those credentials with the provider, and then issue its own token, which will be used by the client as the authentication token to communicate with the service. The diagram above shows a rough picture of the authentication flow. Notice that the client may send more than one request to the authentication provider, as it’s often first asks the user to enter its credentials, then (at least once per application) asks the user to allow the application to use its credentials. What the browser control in the client does is to monitor the URL to where it’s navigating, and when it sees that it’s navigating to the /login/done endpoint, it will know that the whole authentication “dance” has finished. At that point, the client can dispose the browser control and store the token to authenticate future requests it sends. This whole protocol is just a bunch of GET requests and redirect responses. That’s something that a “regular” browser can handle pretty well, so we can use that to make sure that the server is properly set up.
5. I think we should also include the HYBRID option which many of the enterprises are taking up under “Design”
6. I will discuss following four topics in the next 30 minutes How azure helped the Halo 4 team to become successful using cloud technologies. The technologies and concepts which are becoming more relevant and of more concern given cloud technologies and their cost in place. How the cloud technology is changing the eco system around the IT engineering. Last , we will compare different models (Paas , Saas and Iaas) .