Successfully reported this slideshow.

More Related Content

More from Maarten Balliauw

Related Books

Free with a 14 day trial from Scribd

See all

Brewing Beer with Windows Azure

  1. 1. Brewing Beer #warmcrocconf with Windows Azure Maarten Balliauw @maartenballiauw
  2. 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
  3. 3. Setting expectations
  4. 4. Agenda Brewing beer BrewBuddy Windows Azure Websites Service Bus & Access Control Service (ACS) We need an API Q&A
  5. 5. Brewing Beer Turn water into beer
  6. 6. How it started…
  7. 7. How it started… MVP Summit 2011 Wade Wegner talks about his homebrewing hobby MVP Summit 2012 Wade Wegner talks about his homebrewing hobby Convinced!
  8. 8. The process Get your kegs clean Add & boil ingredients Pour in keg Add yeast Rinse
  9. 9. The process Wait for fermentation to complete
  10. 10. The process Pour into another keg Rinse Wait another week Bottling time!
  11. 11. Difficult part… Wait at least 6 weeks for it to age
  12. 12. Maarten… What does this have to do with Windows Azure?
  13. 13. BrewBuddy.net Social brewing!
  14. 14. BrewBuddy View public recipes Manage your own recipes Manage your own brews Monitor brew fermentation
  15. 15. demo BrewBuddy Social brewing at a glance
  16. 16. Architecture Sensor Public website Windows Azure Web Sites Whatever… Database SQL Azure database Sensor data Sensor data processing Service Bus topic Windows Azure Worker Role
  17. 17. Windows Azure Web Sites Scale-fast has just become more interesting
  18. 18. 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
  19. 19. Windows Azure Web Sites shared 1 SHARED INSTANCES
  20. 20. Windows Azure Web Sites shared 2 SHARED INSTANCES
  21. 21. Windows Azure Web Sites reserved 0 1 SHARED INSTANCES RESERVED INSTANCE
  22. 22. Windows Azure Web Sites reserved 2 RESERVED INSTANCE
  23. 23. Windows Azure Web Sites reserved 2 RESERVED INSTANCE RESERVED INSTANCE
  24. 24. 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
  25. 25. demo Windows Azure Web Sites Creating a new web site in seconds
  26. 26. Service Bus & Access Control Service Connecting sensors
  27. 27. Windows Azure Service Bus 2 features Relay Queues, Topics, Subscriptions
  28. 28. Windows Azure Service Bus Relay relay Client
  29. 29. Topics and subscriptions Sensor
  30. 30. Characteristics Workers can scale independently Workers can fail independently Sensors connect to service bus directly No layer in between Cheaper
  31. 31. 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
  32. 32. demo Access Control Service Claims for authZ on Service Bus
  33. 33. Architecture Sensor Public website Windows Azure Web Sites Whatever… Sensor management Database Access Control Service SQL Azure database Sensor data Sensor data processing Service Bus topic Windows Azure Worker Role
  34. 34. How do you link a sensor? Every sensor has its sensor ID Add it as an identity to ACS Grant a “Send” claim
  35. 35. demo Linking a sensor to a brew Registering a sensor with Access Control Service
  36. 36. We need an API
  37. 37. 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)
  38. 38. Twitter & Facebook By show of hands
  39. 39. Make everyone API (as the French say)
  40. 40. 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)
  41. 41. Expose services to 3rd parties Valuable Flexible Managed Supported Have a plan
  42. 42. Reach More Clients
  43. 43. 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!
  44. 44. demo Be detailed! Think about RFC 2324 (HTCPCP)
  45. 45. demo ASP.NET Web API Let’s craft a quick API
  46. 46. What about authN / authZ? API access through OAuth2 Access Control Service to the rescue! Client authorized in BrewBuddy.net Access/refresh tokens through ACS
  47. 47. What about authN / authZ? API Consumer BrewBuddy.net client_id and client_secret access API authorize Initial authorization (yes/no) API implementation access/refresh token register delegation Access Control Service Access/Refresh Token
  48. 48. demo Access Control Service for API’s OAuth2 delegation Install-Package WindowsAzure.Acs.Oauth2 -IncludePrerelease
  49. 49. Takeaways
  50. 50. 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
  51. 51. http://blog.maartenballiauw. be @maartenballiauw http://amzn.to/pronuget Thank you!

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.
  • Show peoplearound the ACS porta. Show identities, claims andrulegroups.
  • ×