Windows server app fabric pdc 2010
•
2 gefällt mir•791 views
Microsoft PDC 2010 viewing party Highlights Windows Server AppFabric's capabilities
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (17)
Ähnlich wie Windows server app fabric pdc 2010
Ähnlich wie Windows server app fabric pdc 2010 (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Windows server app fabric pdc 2010
- 2. VP, GRCT @ BAML Microsoft MVP for Connected Systems (6+ yrs) Member of Business Technology Platform Advisors Author I do: Blog + Twitter + PodCast www.hammadrajjoub.net Twitter @HammadRajjoub Bing me http://www.bing.com/search?q=hamm adrajjoub
- 4. • Windows Azure AppFabric • Windows Server AppFabric
- 6. IIS Worker Process AppFabric Hosting Services IIS Manager AppFabric Caching Services Cache Server Cache Server ASP.NET WF & WCF Apps Windows Apps Cache Client Persisten ce Database Monitorin g Database Cache Confi g Cache Client Cache Server
- 7. IIS 7/WAS IIS Manager .NET 4 WCF & WF Frameworks Persistence SQL Persistence Provider Management APIs (PowerShell 2.0 cmdlets) WF & WCF Management Modules Runtime DatabasesPersistence schema Monitoring schema Monitoring WF ETW Tracking WCF ETW Tracking Messaging Router Service Hosting Web Deploy Tool Visual Studio WF & WCF Project Templates Windows 7, Windows Server 2008 & 2008 R2 Discovery Service Reliablility, Scalablity Availability, Deployment, Control Application Monitoring Routing, Activation Instance Restart Behavior AutoStart Service Workflow Mgmt Event Collector
- 16. <sessionState mode="Custom" customProvider="SessionStoreProvider"> <providers> <add name="SessionStoreProvider" type="Microsoft.ApplicationServer.Caching.DataCacheSessionStor eProvider, Microsoft.ApplicationServer.Caching.Client, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" cacheName=“YourCacheName"/> </providers> </sessionState>
- 20. Windows Server Developer Center MSDN Center for Windows Server AppFabric http://www.microsoft.com/downloads/en/det ails.aspx?FamilyID=7290f7ed-e86b-4114- a452-4f07fa32403d
Hinweis der Redaktion
- 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 on a local PDC 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 (well apart from us Xbox diggers right ;) ) 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 A detailed discussion on Distributed Caching followed by some code deomonstrations 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. http://msdn.microsoft.com/en-us/library/ee677312.aspx
- 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.. Hosting Persistance Monitoring Messaging Power Shell Cmdlet APIs Visual Studio and IIS
- http://msdn.microsoft.com/en-us/library/ee677272.aspx http://msdn.microsoft.com/en-us/library/ee677371.aspx
- http://msdn.microsoft.com/library/cc645013.aspx
- Custom Session Provider included with Cache Just a configuration change enables session state to be cached across a cluster You 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.