Successfully reported this slideshow.
Your SlideShare is downloading. ×

App fabric hybrid computing

Upcoming SlideShare
App fabric introduction
App fabric introduction
Loading in …3

Check these out next

1 of 27 Ad

More Related Content

Slideshows for you (20)


Similar to App fabric hybrid computing (20)


Recently uploaded (20)

App fabric hybrid computing

  1. 1. Building Enterprise Scale Services Using Windows Server AppFabric<br />
  2. 2. Profile<br />VP, GRCT @ BAML<br />Microsoft MVP for Connected Systems (6+ yrs)<br />Member of Business Technology Platform Advisors<br />Author<br />I do: Blog + Twitter + PodCast<br /><br />Twitter @HammadRajjoub<br />Bing me<br />
  3. 3. Agenda <br />Introducing Windows Server AppFabric<br />Architecture<br />Features<br />Distributed Caching <br />Hosting & Management Capabilities<br />Connecting with the Cloud<br />Q n A<br />
  4. 4. Introducing AppFabric<br /><ul><li>Windows Server AppFabric
  5. 5. Windows Azure AppFabric</li></li></ul><li>What is Windows Server AppFabric?<br />Extensions to Application Server role on Windows Server Platform<br />Enhanced hosting, management and caching capabilities <br />Allows faster, more scalable and more manageable applications and services<br />In its first release, it comprises of <br />AppFabric Caching Services (remember Velocity?)<br />AppFabric Hosting Services (remember Dublin?)<br />
  6. 6. What is Windows Server AppFabric?<br />ASP.NETWF & WCF<br />Apps<br />Windows<br />Apps<br /> IIS Worker Process<br />Cache<br />Server<br />Cache<br />Server<br />Cache<br />Server<br />IIS Manager<br />Cache Client<br />Cache Client<br />AppFabric Hosting Services<br />Cache<br />Config<br />AppFabric Caching Services<br />Monitoring Database<br />Persistence Database<br />
  7. 7. What’s under the hood?<br />IIS Manager<br />Visual Studio<br />WF & WCF Management <br />Modules<br />WF & WCF Project Templates<br />Management APIs (PowerShell 2.0 cmdlets)<br />IIS 7/WAS<br />Persistence<br />Monitoring<br />Messaging<br />Hosting<br />ablility, <br />Scalablity<br />Availability, Deployment, Control<br />Application Monitoring<br />Routing, Activation<br />.NET 4 WCF & WF Frameworks<br />Instance Restart<br />Behavior<br />SQL Persistence Provider<br />WF ETW Tracking<br />WCF ETW Tracking<br />Router Service<br />Web Deploy Tool<br />Discovery Service<br />AutoStart Service<br />Workflow Mgmt<br />Event Collector<br />Runtime Databases<br />Persistence schema<br />Monitoring schema<br />Windows 7, Windows Server 2008 & 2008 R2<br />
  8. 8. Architecture<br />
  9. 9. Architecture - contd<br />Runtime Services and Components:-<br />Asp.Net<br />Application Domains<br />Lifecycle and health monitoring<br />Message based activations<br />WCF and WF<br />Building blocks for composite applications<br />Runtime Dbs& Persistence<br />Instance Store, Query & Control Provider<br />
  10. 10. Architecture - contd<br />Hosting<br />Auto-Start<br />Service Management (WMS)<br />App Pool Recycling<br />Monitoring<br />Health and Activity Tracking<br />Event collection<br />Monitoring Dbs<br />Power Shell Cmdlets<br />Dashboard<br />
  11. 11. Distributed Caching<br />
  12. 12. AppFabric Cache<br />Caches any serializable CLR object and provides access through simple cache APIs.<br />Supports enterprise scale: tens to hundreds of computers.<br />Configurable to run as a service accessed over the network<br />Supports dynamic scaling-out by adding new nodes<br />Backup copy provides high availability<br />Automatic load balancing<br />
  13. 13. AppFabric Cache Contd.<br />Integration with administration and monitoring tools such as PowerShell, Event Tracing for Windows, System Center, etc.<br />Provides seamless integration with ASP.NET to be able to cache session data in without having to write it to source databases. It can also be used as a cache for application data to be able to cache application data across the entire Web farm.<br />Follows the cache-aside architecture (also known as Explicit Caching) for V1. That is, you must decide explicitly which objects to put/remove in your applications and the cache does not synchronize with any source database automatically.<br />Types of data: Reference Data, Activity Data and Resource Data...<br />
  14. 14. Demo<br />Simple Caching Client!<br />
  15. 15. Asp.Net Caching Scenario<br />
  16. 16. Demo<br />Asp.Net Caching Provider!<br />
  17. 17. Setting up Asp.Net Caching Provider<br /> <sessionStatemode="Custom"customProvider="SessionStoreProvider"><br /> <providers><br /> <addname="SessionStoreProvider"type="Microsoft.ApplicationServer.Caching.DataCacheSessionStoreProvider, Microsoft.ApplicationServer.Caching.Client, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35"cacheName=“YourCacheName"/><br /> </providers><br /> </sessionState><br />
  18. 18. High Availability Scenario<br />
  19. 19. Hosting capabilities<br />Windows Server AppFabric<br />
  20. 20. Hosting and Management<br />Extension to IIS7 using WAS<br />Hosting and Management of WCF and WF<br />Load balancing 100s of nodes<br />Increased availability<br />Easy to setup base configuration (replicated via msdeploy.exe/xcopy/powershell)<br />Event Collection via ETW for Windows<br />Lifecycle management of durable workflows<br />
  21. 21. Benchmarks<br />
  22. 22. Windows Azure appfabric<br />Connecting with the Cloud<br />
  23. 23. Windows Azure AppFabric<br />Comprehensive Cloud Middleware<br />Developing, deploying and managing applications on the Windows Azure Platform<br />PaaS<br />Enables birdging existing apps to the cloud via secure connectivity<br />Consistent development model on the premise and on the cloud<br />Middleware services + composite applications+ scale out infrastructure<br />
  24. 24. Windows Azure AppFabric<br />.NET + AppFabric Composition Model & Tools<br />AppFabric Management<br />AppFabric Services<br />AppFabric Container<br />SQL Azure<br />SQL Server<br />Windows Azure<br />Windows Server<br />
  25. 25. Middleware Services<br />
  26. 26. Comopsite Applications<br />
  27. 27. What is AppFabric?<br />AppFabric Services<br /> Caching<br /> Service Bus<br /> Access Control<br /> Integration<br /> Composite App (WF, WCF)<br />.NET Composition<br />Management<br />AppFabric Container<br />Multi-tenant, high-density, scaled-out host<br />Composition runtime<br />SQL Server<br />SQL Azure<br />Windows Azure<br />Windows Server<br />
  28. 28. QnA<br />
  29. 29. References<br />Windows Server AppFabric Training Kit<br />Windows Azure AppFabric Training Kit<br />TechEd video from KarandeepAnand<br />

Editor's Notes

  • Hello and welcome to my talk on Windows Server AppFabric, I must say I am super excited to be here in front of you and hosting this talk at an IASA event. Today we are going to discuss what is Windows Server AppFabric and how it is relevant to enterprise development that we do here, day in and day out.
  • So, coming back to ‘the real discussion’ and that’s what I believe we are all here for Here is a quick look at the agenda :- A high level overview of Windows Server AppFabric a look at its architecture, sort of a peek under the hood Quick demo on caching Windows Azure Appfabric Last but not the least QnA
  • Here we go...So, we are talking about Windows Server app Fabric and not the Windows Azure AppFabric...Windows Azure AppFabric is for the Cloud where as Windows Server AppFabric is for on-premise use i.e. It runs on Windows Server Although some of the concepts and API are similar to that of cloud offering but we will still focus on the Windows Server based sibling of AppFabric!
  • Windows Server AppFabric extends Windows Server to provide enhanced hosting, management, and caching capabilities for Web applications and middle-tier services. The AppFabric hosting features add service management extensions to Internet Information Services (IIS), Windows Process Activation Service (WAS), and the .NET Framework 4. This includes Hosting Services and Hosting Administration tools that make it easier to deploy, configure, and manage Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF) based services. The AppFabric caching features add a distributed, in-memory object cache to Windows Server that makes it easier to scale out high-performance .NET applications, especially ASP.NET applications.Services and service-oriented architectures are being built into many types of applications today, from simply exposing some functionality as a service for others to use to an application itself being a complex coordination across many services. The need to construct applications that can easily participate and perform in this services world has never been greater. Modern applications typically have at their heart a data-driven transactional component (such as taking orders on a web site) together with highly distributed business logic that manages these transactions across a middle tier.
  • One of the great truths of building software is this: Application developers shouldn’t spend their time creating infrastructure. Even though every application needs some supporting services, the people who write those applications ought to focus solely on creating value for their users. Whatever infrastructure is required should be provided by the platform they’re building on. Windows Server AppFabric aims to provide a set of extensions to Windows Server, such that windows developers can create faster, more scalable, and more manageable applications.
  • Highlight building blocks..HostingPersistanceMonitoringMessagingPower Shell Cmdlet APIsVisual Studio and IIS
  • Custom Session Provider included with CacheJust a configuration change enables session state to be cached across a clusterYou may want to enable HA on the cache used
  • AppFabric Caching Services stores all cached data in memory—it’s not written to disk. By default, each cached object is stored on only one machine in a cache cluster. To improve resilience if a cache server goes down, AppFabric Caching Services has a high-availability option that creates a secondary copy of each cached data item on another machine in the cluster. If the cache server holding the primary copy of this data fails, the secondary remains available. This example shows a read, but updates also work when the cache server holding a primary copy goes down. Once AppFabric Caching Services detects that the primary is unavailable, it promotes the existing secondary copy to a primary, then creates a new secondary copy. None of this is visible to the cache client—everything works just as if no failure had occurred. Whether or not the high-availability option is used, AppFabric Caching Services speeds up access to frequently accessed data. This is a good thing—it’s a useful addition to the application infrastructure provided by Windows Server. Providing better support for an application’s logic is also useful, however. How Windows Server AppFabric does this is described next.
  • Event collection:-The first AppFabric Windows service is the Event Collection service. Up to ten Event Collection service instances can run on a single server. Based upon the configured monitoring level, its role is to gather WCF and WF instrumentation events emitted by the .NET Framework runtime into an Event Tracing for Windows (ETW) session.  The Event Collection service then stores these events in the monitoring database. AppFabric uses event data to aggregate information about overall status of applications to assist in performance monitoring and troubleshooting. AppFabric Workflow Management ServiceThe second AppFabric Windows service is the Workflow Management service, which the hosting services use to manage instances of workflows.  The Workflow Management service activates a workflow service instance in an instance store when the instance is eligible to be activated.  The Workflow Management service retrieves commands from a message queue that is written to by an instance control provider, executes the commands, and then deletes commands from the queue if the command execution is successful.
  • Service Bus (Commercially available now; updated CTP delivered October 2010) provides secure messaging and connectivity capabilities that enable building distributed and disconnected applications in the cloud, as well as hybrid applications across both on-premise and the cloud. It enables using various communication and messaging protocols and patterns, and removes the need for the developer to worry about delivery assurance, reliable messaging and scale. Access Control (Commercially available now; updated CTP delivered August 2010) enables an easy way to provide identity and access control to web applications and services, while integrating with standards-based identity providers, including enterprise directories such as Active Directory®, and web identities such as Windows Live ID, Google, Yahoo! and Facebook.Caching (New CTP service delivered October 2010; commercially available in H1 CY11) accelerates performance of Windows Azure and SQL Azure based apps by providing a distributed, in-memory application cache, provided entirely as a service (no installation or management of instances, dynamically increase/decrease cache size as needed). Pre-integration with ASP.NET enables easy acceleration of web applications without having to modify application code.Integration (New CTP service coming in CY11) will provide common BizTalk Server integration capabilities (e.g. pipeline, transforms, adapters) on Windows Azure, using out-of-box integration patterns to accelerate and simplify development. It will also deliver higher level business user enablement capabilities such as Business Activity Monitoring and Rules, as well as self-service trading partner community portal and provisioning of business-to-business pipelines.Composite App (New CTP service coming in H1 CY11) will provide a multi-tenant, managed service which consumes the .NET based Composition Model definition and automates the deployment and management of the end to end application - eliminating manual steps needed by both developers and ITPros today. It also executes application components to provide a high-performance runtime optimized for cloud-scale services and mid-tier components (automatically delivering scale out, availability, multi-tenancy and sandboxing of application components). Finally, it delivers a complete hosting environment for web services built using Windows Communication Foundation (including WCF Data Services and WCF RIA Services) and workflows built using Windows Workflow Foundation. It’s a key characteristic of all AppFabric Middleware Services that they are consistently delivered as true multi-tenant services – you simply provision, configure, and use (no installation or management of machines/instances).
  • Microsoft is advancing its Windows Azure AppFabric cloud middleware platform to provide a full composite application environment for developing, deploying and managing composite applications. The AppFabric composition environment delivers three main benefits: Composition Model A set of .NET Framework extensions for composing applications on the Windows Azure platform. This builds on the familiar Azure Service Model concepts and adds new capabilities for describing and integrating the components of an application. It also provides a consistent composition model for both Windows Azure and Windows Server.Visual Design Experience A new Visual Studio based designer experience allows you assemble code from your existing application components, along with newer cloud services, and tie them together as a single logical entity.Managed as a service The Composite Application service is a multi-tenant, managed service which consumes the Composition Model definition and automates the deployment and management of the end to end application - eliminating manual steps needed by both developers and ITPros today. The composite application environment offers the following benefits:Greater developer productivity through rapid assembly, linking of components and automated deployment of the entire end-to-end application;Easier configuration and control of entire application and individual components;End-to-end application monitoring (events, state, health and performance SLAs);Easier troubleshooting (through richer diagnostics and debugging of the whole application);Performance optimization of the whole application (scale-out/in, fine-tuning, migration, etc); Integrated operational reporting (usage, metering, billing).