Presentation is loading. Please wait.

Presentation is loading. Please wait.

4/20/2017 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks.

Similar presentations


Presentation on theme: "4/20/2017 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks."— Presentation transcript:

1 4/20/2017 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2 Windows Azure Cloud & Application Services
Name Title Organization

3 Agenda A brief review of Cloud Service Inter-role communication
4/20/2017 Agenda A brief review of Cloud Service Inter-role communication Windows Azure Cloud Service Lifecycle Dedicated cache Windows Azure Service Bus Windows Azure Access Control Service © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4 Azure ecosystem Hello World! . Gallery Social N-Tier LOB Legacy SPA
Control Flexibility Gallery Social N-Tier LOB Legacy Management Complexity SPA Sharing Web API Hybrid Specialized On-prem Slide Objectives: Introduce Azure application ecosystem. Point out that Web Sites, Cloud Service, and Virtual Machines provide a continuous landscape of application development and hosting. Speaking Points: Azure building block services are available across the landscape. Emphasize how Azure can provide robust infrastructure with *global reach* that allows you to reach out to more customers. Notes: This talk usually happens after initial overview of Azure. The assumption is that audience has heard the terms “Web Site”, “Cloud Service”, and “Virtual Machines”. This slide is to put everything into perspective so that the audience can understand the three areas are not isolated offerings. Web Sites Cloud Services Virtual Machines Caching Access Control Service Bus CDN SQL Database Traffic Manager HPC Storage Media Services

5 Azure ecosystem Hello World! . Gallery Social N-Tier LOB Legacy SPA
Control Flexibility Gallery Social N-Tier LOB Legacy Management Complexity SPA Sharing Web API Hybrid Specialized On-prem Caching Access Control Service Bus CDN SQL Database Traffic Manager HPC Storage Media Services

6 Azure ecosystem Hello World! . Gallery Social N-Tier LOB Legacy SPA
Control Flexibility Gallery Social N-Tier LOB Legacy Management Complexity SPA Sharing Web API Hybrid Specialized On-prem Caching Access Control Service Bus CDN SQL Database Traffic Manager HPC Storage Media Services

7 Azure ecosystem Hello World! . Gallery Social N-Tier LOB Legacy SPA
Control Flexibility Gallery Social N-Tier LOB Legacy Management Complexity SPA Sharing Web API Hybrid Specialized On-prem Caching Access Control Service Bus CDN SQL Database Traffic Manager HPC Storage Media Services

8 Cloud Service Overview
4/20/2017 Cloud Service Overview © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9 Why Cloud Service? Build infinitely scalable applications and services
4/20/2017 Why Cloud Service? Build infinitely scalable applications and services Support rich multi-tier architectures Automated application management © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10 A collection of related service roles
What is a Cloud Service? A collection of related service roles Web Role Worker Role Slide Objectives: A brief definition of Cloud Service. Speaking Points: Cloud Service defines management, security, deployment, and communication boundary of your services. Notes: This definition emphasize that Cloud Service is a container.

11 What Can It Run? General Rule Choice of Language Choice of Frameworks
If it runs in Windows it can run as a Cloud Service C#, VB, C++, Java, PHP, Node.js, Phython, etc. .NET, ExpressJS, Rails, Zend, etc.

12 Web Role All features of a worker role + IIS 7 or 7.5
ASP.NET 3.5 SP1 or 4.0 – 64bit Hosts Webforms or MVC FastCGI applications (e.g. PHP) Multiple Websites Http(s) Web/Worker Hybrid Can optionally implement RoleEntryPoint Slide Objective: Understand how a Web Role extends the standard worker role Speaker Notes: A web role takes all the capabilities and semantics of a worker role and adds the IIS Hostable Web Core Web Roles run ASP.NET websites- they do this by using the IIS hostage web core. pretty much anything that will work in a standard IIS ASP.NET Web Site should work in Windows Azure. At MIX09, we additionally added support for IIS7’s FastCGI capability. As a note, any files that are part of a asp.net project on windows azure are READ ONLY! If you need to be able to change the contents of files: User Blob Storage If its configuration, use the service model files – which can be changed at runtime. Inbound protocols are http(s) – outbound protocols are any TCP connection but NOT UDP. Notes:

13 Worker Role Patterns Queue Polling Worker Listening Worker Role
Poll and Pop Messages within while(true) loop E.g. Map/Reduce pattern, background image processing Listening Worker Role Create TcpListener or WCF Service Host E.g. Run a .NET SMTP server or WCF Service External Process Worker Role OnStart or Run method executes Process.Start() Startup Task installs or executes background/foreground process Custom Role Entry Point (executable or .Net assembly) E.g. Run a database server, web server, distributed cache Slide Objective: Understand the 3 common patterns of worker roles Speaker Notes: Pattern 1 – Polling Worker role polls a Queue Pops message Performs work Polls queue again Pattern 2 Worker listens for inbound TCP request Can implement with Raw TcpListeners or use WCF or use Hosted Web Core Pattern 3 Run a 3rd party process When the role starts up or runs use a Process.Start() call to run a standard windows executable E.g. Running a database server Notes:

14 Role Lifecycle All roles may extend RoleEntryPoint Roles report status via RoleEnvironment Methods Events Status Fabric Calls OnStart StatusCheck Busy Requests Routed Run StatusCheck Ready Role Lifetime Slide Objective: Understand the lifecycle of a Windows Azure role Understand the methods that can be overridden in RoleEntryPoint Understand the events that are raised by role instances when their status is changing Speaker Notes: Roles will typically extend RoleEntryPoint The fabric calls RoleEntryPoint methods as it starts and stops a role WaWorkerHost process is started. Worker Role assembly is loaded and surfed for a class that derives from RoleEntryPoint. This class is instantiated. RoleEntryPoint.OnStart() is called. RoleEntryPoint.Run() is called. If the RoleEntryPoint.Run() method exits, the RoleEntryPoint.OnStop() method is called . WaWorkerHost process is stopped. The role will recycle and startup again. As a role changes state it will raise the StatusCheck event. A status of Busy will mean the load balancer will not route requests to the instance. Notes: OnStop StatusCheck Busy Stopping

15 Roles and Instances Roles are defined in a Hosted Service
A role definition specifies: Virtual machine size Communication endpoints Local storage resources etc. At runtime each Role will execute on one or more instances A role instance is a set of code, configuration, and local data, deployed in a dedicated VM Slide Objective: Understand the difference between Roles and Instances Speaker Notes: The Service model defines the shape of a service- the Roles it will have endpoints it will listen on Types of VMs that will be run At runtime each Role will run at a given scale Specifically each role will be deployed onto and executed on one or more VMs A VM runs a single role Notes: Notes on the various security roles involved in running a Windows Azure account

16 Roles and Instances Cloud Service Web Roles Worker Roles
4/20/2017 7:32 PM Roles and Instances Worker_instance_0 Cloud Service Worker_instance_1 Web Roles Worker Roles Worker_instance_2 Web_instance_0 Slide Objective: This animation is to reinforce the message in previous slide by showing how roles and mapped to instances during deployment. Web_instance_1 © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17 Fault Domains 99.95% Uptime Guarantee
Requires 2 or more instance per role Role instance are isolated by fault domain Fault domains isolate VMs Fault domains provide redundancy At least two fault domains per role Notes: The infrastructure of each Windows Azure data center is notionally divided into multiple sections known as fault domains. These sections of the infrastructure (which are not necessarily individual servers or server racks) are designed in such a way that a failure of one fault domain is extremely unlikely to affect any other fault domain. When you deploy a service, the Windows Azure Fabric Controller automatically locates the roles in at least two different fault domains so that a failure in one domain will not affect all instances of your service.

18 Roles and Instances Example role with nine virtual machines distributed across three fault domains
Network Load Balancer Role Fault Domain 1 Fault Domain 2 Fault Domain 3 VM1 VM3 VM2 VM4 VM6 VM9 Slide Objective: Understand what a scale-out application looks like Speaking notes: High scale applications often follow this sort of an pattern Inbound connectivity comes through a load balancer Requests are round robin routed Load balancer is typically aware of the state of the web servers (i.e. are they up) There are one or more tiers or groups of stateless web or app servers By stateless we mean that they do not hold state between client requests Stateless means that simple load balancing works – no need for sticky sessions Stateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancer A stateful or storage tier This will generally involve some sort of scale out approach for large apps Often using partitioned databases Often some sort of queuing mechanism Applications will often perform processing in the background. Improves response time for users Allows load peaks to be buffered in queues Windows Azure provides us with a Platform as a Service offering to implement these sorts of applications Notes: VM5 VM8 VM6 VM9

19 Logical unit, which determines how particular service will be upgraded
Upgrade Domains Logical unit, which determines how particular service will be upgraded Default number of upgrade domains that are configured for your application is 5 (five) You can control how many upgrade domains your application will use through the

20 Cloud Service – inter-role communication
4/20/2017 7:32 PM Cloud Service – inter-role communication Internal Endpoint Not load-balanced HTTP/TCP/UDP/ANY Input Endpoint Load-balanced HTTP/HTTPS/TCP/UDP Other options Queue Storage Database Instance Input Endpoint Route traffic to specific instance based on port TCP/UPD © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21 Demo description Create a new cloud service project
4/20/2017 Demo description Create a new cloud service project Add a web role and a worker role Add a HttpListener to worker role Define Internal endpoint on worker role Send requests from web role to specific instance Show how to define InstanceInput endpoint Demonstrate addressing instance using a deployed service (doesn’t work on local emulator) © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

22 Inter-role communication
Demo Inter-role communication

23 Demo description Create a new website, publish, change, publish again
4/20/2017 Demo description Create a new website, publish, change, publish again Add a cloud service project Add a worker role Scale the roles Publish (enabled RDC) Show existing deployment Examine service definition file RDC to role instance © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24 Demo Hello World How to use portal to manage cloud services

25 Cloud Service Lifecycle
4/20/2017 Cloud Service Lifecycle © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

26 Understanding Packaging and Config
Windows Azure Services are described by two artifacts: Service Definition (*.csdef) Service Configuration (*.cscfg) Your code is zipped and packaged with definition (*.cspkg) Encrypted(Zipped(Code + *.csdef)) == *.cspkg Windows Azure consumes just (*.cspkg + *.cscfg)

27 Runtime Settings Startup tasks Remote Desktop support Endpoints
4/20/2017 Runtime Settings Startup tasks Install software and features Configure host environment Start processes Remote Desktop support Certificate used to enable remote desktop access Endpoints Public endpoints Internal endpoints InstanceInput endpoints © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

28 Packaging & Deployment
Service Artefacts Upload to Windows Azure Microsoft Visual Studio Web Role Worker Role *.cspkg Windows Azure Compute Controller Model Config *.cscfg LB Slide Objective CODE – PACKAGE – UPLOAD – DEPLOY Shows how service makes it from code living in Visual Studio to a running deployed instance in Windows Azure Show how Roles are packaged up and uploaded with the config to Windows Azure Speaking Points Code is compiled, then packaged into a single file. This is the service package. This, along with the configuration/service model – are deployed via the web portal. Notes Visual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api Visual Studio Tools for Windows Azure now supports one-click deployment. Aimed at rapid build/deploy/test/fix scenarios. Service You can also integrate with source control such as TFS and deploy via continuous integration

29 Application Upgrade Strategies
4/20/2017 Application Upgrade Strategies Staging vs. Production Deploy to staging for testing and validation; Promote to production using VIP swap In-place upgrade Replace an old deployment with a new deployment © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

30 Demo description Create a new website, publish, change, publish again
4/20/2017 Demo description Create a new website, publish, change, publish again Add a cloud service project Add a worker role Scale the roles Publish (enabled RDC) Show existing deployment Examine service definition file RDC to role instance © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

31 Demo Service Management How to use portal to manage cloud services

32 Cloud service lifecycle – Simplistic view
Code Package Upload Deploy Slide Objective: CODE – PACKAGE – UPLOAD – DEPLOY Shows how service makes it from code living in Visual Studio to a running deployed instance in Windows Azure Show how Roles are packaged up and uploaded with the config to Windows Azure Speaking Points: Code is compiled, then packaged into a single file. This is the service package. This, along with the configuration/service model – are deployed via the web portal. Notes: Visual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api

33 Cloud service lifecycle - Agile
Daily scrum Sprint planning Product planning Sprint Shippable increment Slide Objectives: This is a typical lifecycle of SCRUM. The previous lifecycle pattern may suite for simple development for individuals and very small teams; to support real-life workflows, we need more than packaging and deploying. Good news is that now TFS is integrated into Azure.

34 Team Foundation Service
4/20/2017 7:32 PM Team Foundation Service Governance/Guidance over complete software lifecycle Integrated with Visual Studio, and now Azure Management Portal Support different methodologies and processes Source repository with gated check-in Continuous integration with auto-build Integrated bug tracking © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

35 Demo description Demonstrate TFS enablement process on portal
4/20/2017 Demo description Demonstrate TFS enablement process on portal Demonstrate connecting to TFS from VS Map to local folder Initiate a commit © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

36 TFS Continuous Integration
Demo TFS Continuous Integration

37 Windows Azure Diagnostics
Role Instance Starts Diagnostic Monitor Starts Monitor is configured Imperatively at Start time Remotely any time Configuration is saved in Storage Monitor buffers data locally User can set a quota (FIFO) User initiates transfer to storage from local buffer Scheduled On Demand Role Instance Role Diagnostic Monitors Local directory storage

38 Windows Azure Diagnostics
Demo Windows Azure Diagnostics Demonstrate code & result of custom counters

39 Application building blocks
Big data Database Storage Traffic Caching Messaging Identity Application building blocks Media CDN Networking

40 Application building blocks
Big data Database Storage Traffic Caching Messaging Identity Application building blocks Media CDN Networking

41 What’s Windows Azure Cache?
4/20/2017 7:32 PM What’s Windows Azure Cache? Use spare memory on your VMs as high-performance cache Distributed cache cluster co-located with existing roles, or use dedicated roles Named caches with high availability option Notifications Support Memcached protocol Note: Previously known as “dedicated cache”, or “co-located cache”, or “cache (preview)” is not known as Windows Azure Cache. And previous “Windows Azure Cache”, or “Windows Azure Caching Service” is now Windows Azure Shared Cache. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

42 Why Windows Azure Cache?
4/20/2017 7:32 PM Why Windows Azure Cache? Faster No external service calls (additional network hops) Co-located in roles Cheaper No external service calls (additional cost) Use spare memory that you already paid for More reliable Your service is running = cache is available No throttling as in cotenant environment © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

43 Demo description Demo Twitter Reader
4/20/2017 Demo description Demo Twitter Reader © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

44 Demo Windows Azure Cache Note: Twitter Reader is a good sample to show

45 Memcached support Host a Memcached cluster in Work Roles
4/20/2017 7:32 PM Memcached support Host a Memcached cluster in Work Roles Access a Memcached cluster from Web/Worker Roles Web/Worker Role Cache worker role Web/Worker Role Web/Worker Role M Memcached Shim Memcached Shim M M Memcached Client Memcached Server © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

46 Demo description Demo enabling public access
4/20/2017 Demo description Demo enabling public access Demo Java Memcached client accessing caching cluster © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

47 Memcached Interoperability
Demo Memcached Interoperability

48 Application building blocks
Big data Database Storage Traffic Caching Messaging Identity Application building blocks Media CDN Networking

49 Cloud/On-Premise Integration
Cloud-Hosted, reliable asynchronous Messaging Infrastructure with Publish/Subscribe Cloud-Based Relay enabling NAT/Firewall Traversal for reach into on-premises assets Cloud App On-Prem assets

50 NAT Firewall Dynamic IP
Relay Service Bus Relay solves the challenges of communicating between on-premises applications and the outside world by allowing on-premises web services to project public endpoints. Systems can then access these web services, which continue to run on-premises from anywhere on the planet. Service Bus Sender Receiver NAT Firewall Dynamic IP

51 Messaging Queue Topic & Subscription S R Queue
4/20/2017 Messaging Queue Asynchronous communication Offline processing Load-balancing Topic & Subscription Asynchronous communication Publish/Subscription pattern Message routing Queue S R Queue S R © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

52 Demo description Demo Service bus relay
4/20/2017 Demo description Demo Service bus relay © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

53 Demo Service Bus: Relay

54 Application building blocks
Big data Database Storage Traffic Caching Messaging Identity Application building blocks Media CDN Networking

55 Security challenge Your App Customer support Data protection
Management UI Forget password? User store User mapping LDAP More User mapping Authentication Authorization Slide Objectives: Security is a common request of applications. However implementing **proper** security is hard. Also, additional security-related code increases complexity and attacking service to your applications. We need authentication and authorization abstracted away so we can focus on business logics. Synchronization Integration with AD Facebook Auth API Your App More Synchronization Integration With Facebook

56 Solution: Claim-based architecture
ACS + WIF ? “User is Joe” “Role is Administrator” Slide Objectives: Wouldn’t it be nice if “someone” can hide all complexities and just provides simple assertions to us? On Windows Azure, this “someone” is ACS + WIF. Your App

57 Digital identity in a nutshell
Claim: Seat is 28A RP Token IdP Token Home Realm Discovery WIF ACS IdP User

58 ACS Browser-based WIF Rich Client Mobile Identity Providers ACS
Your Application Browser-based WIF SAML SWT WS-Federation Claims ADFS2 . WS-Federation Notes: The ACS would deserve multiple sessions on its own right to be properly covered, here I'm just giving you a quick sampler. What we have seen so far is just a small part of its surface. The schema here shows the ws-federation subsystem, what is normally used for browser-based, session-oriented application types. We've been playing only with ADFS IP types, but in fact <click> there are many out of the box popular IPs you can use right away with your application sticking to the same protocol <click> and a browser<click>. ACS can also do WS-Trust, a high-security protocol for SOAP web services, accepting identities from ADFS2 ws-trust endpoints or bare credentials registered in ACS for management purposes. <click> the same sources can be used within OAuth2.0 calls. OAuth is the current state of the art for securing REST calls: it is still in draft state, hence expect changes, but you can already experiment with it. <click> Both protocols can be used for rich client application types and in general <click> server 2 server interactions. Not shown here there are the management endpoints, the other portion of ACS' development surface, which can be used instead or alongside the portal for managing the namespace. Rich Client SAML WS-Trust ADFS2 . WS-Trust Mobile SWT OAuth WRAP/2.0 Service Identities

59 Demo description Demo ADFS and ACS
4/20/2017 Demo description Demo ADFS and ACS Deployed: haishiadfs.cloudapp.net ADFS: haishi2008r2.cloudapp-preview.net User: cloudapp-preview.net\user pass: TopSecret$123 Admin: cloudapp-preview.net\admin pass:TopSecret$123 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

60 Federated security with ACS
Demo Federated security with ACS Notes: Use ACS to manage accesses using ADFS, Microsoft ID and Google ID

61 4/20/2017 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.


Download ppt "4/20/2017 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks."

Similar presentations


Ads by Google