Brewing Beer with Windows Azure - NDC2013
•Download as PPTX, PDF•
1 like•1,634 views
This document discusses building a social brewing application called BrewBuddy using Windows Azure technologies. It describes the brewing process, the BrewBuddy application architecture using Azure Web Sites, Service Bus, and Access Control Service. It also covers developing an API for BrewBuddy using ASP.NET Web API and Access Control Service for authentication.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Brewing Beer with Windows Azure - NDC2013
Similar to Brewing Beer with Windows Azure - NDC2013 (20)
More from Maarten Balliauw
More from Maarten Balliauw (20)
Recently uploaded
Recently uploaded (20)
Brewing Beer with Windows Azure - NDC2013
- 1. Brewing Beer with Windows Azure Maarten Balliauw @maartenballiauw
- 2. Who am I? Maarten Balliauw Technical Evangelist, JetBrains AZUG Focus on web ASP.NET MVC, Windows Azure, SignalR, ... MVP Windows Azure & ASPInsider http://blog.maartenballiauw.be @maartenballiauw Shameless self promotion: Pro NuGet - http://amzn.to/pronuget http://www.myget.org
- 7. Agenda Brewing beer BrewBuddy Windows Azure Websites Service Bus & Access Control Service (ACS) We need an API Q&A
- 8. Brewing Beer Turn water into beer
- 10. How it started… MVP Summit 2011 Wade Wegner talks about his homebrewing hobby MVP Summit 2012 Wade Wegner talks about his homebrewing hobby Let’s do it!
- 11. The process Get your kettle clean Add & boil ingredients Pour in kettle Add yeast Rinse
- 13. The process Wait for fermentation to complete
- 14. The process Pour into another kettle Rinse Wait another week Bottling time!
- 15. Difficult part… Wait at least 6 weeks for it to age
- 17. Maarten… What does this have to do with Windows Azure?
- 19. BrewBuddy View public recipes Manage your own recipes Manage your own brews Monitor brew fermentation
- 20. demo BrewBuddy Social brewing at a glance
- 21. Architecture Public website Windows Azure Web Sites Database SQL Azure database Sensor data processing Windows Azure Worker Role Sensor data Service Bus topic Sensor Whatever…
- 22. Windows Azure Web Sites Scale fast, fail fast
- 23. Windows Azure Web Sites Build with ASP.NET, Node.js or PHP Deploy in seconds with FTP, Git or TFS Start for free, scale up as your traffic grows
- 24. 1 SHARED INSTANCES shared Windows Azure Web Sites
- 25. 2 SHARED INSTANCES shared Windows Azure Web Sites
- 26. SHARED INSTANCES 1 RESERVED INSTANCE 0reserved Windows Azure Web Sites
- 27. 2 RESERVED INSTANCERESERVED INSTANCE reserved Windows Azure Web Sites
- 28. 2 RESERVED INSTANCE RESERVED INSTANCE reserved Windows Azure Web Sites
- 29. A perfect ramp-up! Start small Web Sites are cheap Start free Scale from 1 shared instance… …up to 10 reserved instances! Grow big! Hosted Service – PaaS Scale at will
- 30. demo Windows Azure Web Sites Creating a new web site in seconds
- 31. Service Bus & Access Control Service Connecting sensors
- 32. Windows Azure Service Bus 2 features Relay Queues, Topics, Subscriptions
- 33. Windows Azure Service Bus Relay Client relay
- 35. Characteristics Workers can scale independently Workers can fail independently Sensors connect to service bus directly No layer in between Cheaper
- 36. What about authN / authZ? Access Control Service to the rescue! SB authenticates clients over ACS ACS provides “Send” claim to sensor Claims can be granted/revoked easily
- 37. demo Access Control Service Claims for authZ on Service Bus
- 38. Public website Windows Azure Web Sites Database SQL Azure database Sensor data processing Windows Azure Worker Role Sensor management Access Control Service Sensor data Service Bus topic Sensor Whatever… Architecture
- 39. How do you link a sensor? Every sensor has its sensor ID Add it as an identity to ACS Grant a “Send” claim
- 40. demo Linking a sensor to a brew Registering a sensor with Access Control Service
- 41. We need an API
- 42. Consuming the web 2000-2008: Desktop browser 2008-2012: Mobile browser 2008-2012: iPhone and Android apps 2010-2014: Tablets, tablets, tablets 2014-2016: Your fridge (Internet of Things)
- 44. Twitter & Facebook By show of hands
- 45. Make everyone API (as the French say)
- 46. What is an API? Software-to-Software interface Contract between software and developers Functionalities, constraints (technical / legal) Programming instructions and standards Open services to other software developers (public or private)
- 47. Expose services to 3rd parties Valuable Flexible Managed Supported Have a plan
- 49. ASP.NET Web API Part of ASP.NET MVC 4 Framework to build HTTP Services (REST) Solid features Modern HTTP programming model Content negotiation (e.g. Xml, json, ...) Query composition (OData query support) Model binding and validation (conversion to .NET objects) Routes Filters (e.g. Validation, exception handling, ...) And more!
- 50. demo Be detailed!Think about RFC 2324 (HTCPCP)
- 51. demo ASP.NET Web API Let’s craft a quick API
- 52. A lot of public API’s… “your API consumer isn’t really your user, but an application acting on behalf of a user” (or: API consumer != user)
- 53. So they do this!
- 54. In our own API, authN / authZ API access using OAuth2 Access Control Service to the rescue! Client authorized in BrewBuddy.net Access/refresh tokens through ACS
- 55. What about authN / authZ? Access Control Service Access/Refresh Token API Consumer client_id and client_secret BrewBuddy.net Initial authorization (yes/no) API implementation authorize register delegationaccess/refresh token access API
- 56. demo Access Control Service for API’s OAuth2 delegation Install-Package WindowsAzure.Acs.Oauth2 -IncludePrerelease
- 57. Takeaways
- 58. Keep in mind… Web Sites start cheap / scale fast Combine/grow at will (IaaS, PaaS, SaaS) Service bus for asynchrony and scale Access Control for devices Web API & Access Control
Editor's Notes
- Maarten
- Don’t show everythingyet. Just log in, show themaround the recipes, brewsand public recipes. Feel free to show the monitoring but no needto display the linking of sensors.
- Show Windows Azure Web SitesShow scaling / reservedinstances
- Show peoplearound the ACS porta. Show identities, claims andrulegroups.
- Link a sensor to a brew. Show the effect on ACS. Show the code.
- A couple of years ago, having a web-based application was enough. Users would navigate to it using their computer’s browser, do their dance and log out again. Nowadays, a web-based application isn’t enough anymore. People have smartphones, tablets and maybe even a refrigerator with Internet access on which applications can run. Applications or “apps”. We’re moving from the web towards apps.
- A great example of an API is Twitter. They have a massive data store containing tweets and data related to that. They have user profiles. And a web site. And an API. Are you using www.twitter.com to post tweets? I am using the website, maybe once a year. All other tweets come either from my Windows Phone 7’s Twitter application or through www.hootsuite.com, a third-party Twitter client which provides added value in the form of statistics and scheduling. Both the app on my phone as well as the third-party service are using the Twitter API. By exposing an API, Twitter has created a rich ecosystem which drives their real value: data.
- If you want to expose your data and services to external third-parties, you may want to think about building an API. Having an API gives you a giant advantage on the Internet nowadays. Having an API will allow your web application to reach more users. App developers will jump onto your API and build their app around it. Other websites or apps will integrate with your services by consuming your API. The only thing you have to do is expose a valuable, managed and supported API and get people to know it. Apps will come. Integration will come.
- The mainidea of API’s is tobroadenyourreach. Youcan’tcreateappsthatcanbeused on every fridge out there, it’s way toocostly. But ifyou have a valuable service which is supported, peoplewillbuildappsaround it. Andifitmakes sense toanyonetocreate a fridge app on top of your API, itwill happen.
- Be detailed! Usegood status code responses. 201 CREATED is probablybetterthanjust 200 OK whencreating a new entity.+ demo Fiddleragainst HTCPCP deployment out there
- Link a sensor to a brew. Show the effect on ACS. Show the code.
- I want you to remember one sentence: “your API user isn’t really your user, but an application acting on behalf of a user”. It has implications. It means you are “delegating” access to an API to a consuming application.
- As anexample, take lanyrd.com. They keep track of conferences you’llbespeaking at and conferences thepeopleyou follow on Twitter are speaking at. To get that data, theyneed access to the list of peopleyou follow on Twitter. Here’swhathappens:You want to log in on Lanyrd, theyredirectyoutoTwitter’s login page. Notice the token in the address bar: itidentifies the callingapplicationtoTwitter.You log in on Twitterandgive consent with a limited scope: Lanyrdwillbeabletoseeyourtimelineand get the list of peopleyou follow. The scope is limitedtothat: Lanyrdcan’ttweet on mybehalf. Theycan’tfavoritetweets. Or sendmessages. Or do anythingelse.Twitterredirects me back toLanyrd, posting back a “refresh” tokenWhatyoudon’tsee:Lanyrdusesthat token torequestan “access token” fromTwitter.Twitter checks the validity of the incoming token and checks the origin, to make sure no otherapplication but Lanyrdcomes in withthat token.Whenvalid, Twitter returns an access token toLanyrd, containing:An access keyA new refresh tokenThe allowed scopeValiditydurationA signature- When the token expires, Lanyrduses the new refresh token to go throughthisprocessagain.
- Show peoplearound the ACS porta. Show identities, claims andrulegroups.