AppFabric

AppFabric is a set of middleware technologies for Windows Server, released by Microsoft. It consists of two main feature areas: AppFabric Hosting and AppFabric Caching. Microsoft support for these will end in November 2017. The recommended alternative for caching is Redis.[1]

AppFabric Hosting

AppFabric Hosting features provide a way for users to deploy and manage Windows Workflow Foundation (WF) workflows that are hosted in Windows Communication Foundation (WCF) services.[2] AppFabric includes an extension of the Internet Information Services management tool that enables an IIS administrator to monitor the performance of services and workflows.[3] There is also a set of Windows PowerShell commands to manage persistence, hosting, and monitoring tasks.[4]

AppFabric Hosting features provide three main capabilities for services:

Persistence

Persistence allows Windows Workflow Foundation services to save the state of long running workflows to a database. This makes Workflow services more durable in the event of deliberate suspensions or unexpected hardware failures.[5]

Hosting

Hosting facilitates the management of WCF and WF services within IIS and the Windows Process Activation service (WAS).[6]

Monitoring

Monitoring stores and correlates service events in a backend database. This facilitates analysis and troubleshooting of the coordination of multiple WCF and WF services.[7]

AppFabric Caching

AppFabric Caching is an in-memory, distributed cache that runs on one or more on-premises servers to provide a performance and scalability boost for .NET Framework applications. AppFabric caches store data in key-value pairs using the physical memory across multiple servers. The service presents that memory as a single resource.[8] Caches are configured and managed through a set of Windows PowerShell commands.[9]

ASP.NET caching providers

One use of Caching is to store ASP.NET session state data.[10] When a user connects to an ASP.NET Web application, the application can store information in session state. This can be used in subsequent requests from the same user. Rather than store that information in-memory on each web server, a built-in session state provider can route session data to a backend cache. This enables the ASP.NET application to store large amounts of cached data. It also allows future user requests to route to any web server, because each web server references the same backend cache.[11]

In addition to the ASP.NET session state provider, there is also a provider for ASP.NET page output caching.[12]

Caching API

.NET applications can directly use the Caching API[13] to programmatically cache and retrieve any serializable managed objects.

History

In June 2010, Microsoft released Windows Server AppFabric 1.0.[14] The next release, 1.1, was rebranded to Microsoft AppFabric 1.1 for Windows Server.[15] There are several updates following the 1.1 release:

In April 2015, Microsoft announced that it would end support for AppFabric for Windows Server on 2nd April 2016.[23]
In June 2015, Microsoft announced that it would end support for AppFabric 1.1 for Windows Server on 11th April 2017, with Extended Support being available until 12th April 2022.[24]

References

  1. ↑ http://blogs.msdn.com/b/appfabric/archive/2015/04/02/windows-server-appfabric-1-1-ends-support-4-2-2016.aspx
  2. ↑ "AppFabric Hosting Architecture Diagram". MSDN Library. Microsoft. Retrieved 14 February 2013.
  3. ↑ "Using the AppFabric Management User Interface". MSDN Library. Microsoft. Retrieved 14 February 2013.
  4. ↑ "Using Windows PowerShell Cmdlets in AppFabric". MSDN Library. Microsoft. Retrieved 14 February 2013.
  5. ↑ "Persistence Concepts". MSDN Library. Microsoft. Retrieved 14 February 2013.
  6. ↑ "Hosting Concepts". MSDN Library. Microsoft. Retrieved 14 February 2013.
  7. ↑ "Monitoring Concepts". MSDN Library. Microsoft. Retrieved 14 February 2013.
  8. ↑ "AppFabric Caching Physical Architecture Diagram". MSDN Library. Microsoft. Retrieved 14 February 2013.
  9. ↑ "Using Windows PowerShell to Manage AppFabric 1.1 Caching Features". MSDN Library. Microsoft. Retrieved 13 February 2013.
  10. ↑ "Session State Provider (AppFabric 1.1 Caching)". MSDN Library. Microsoft. Retrieved 14 February 2013.
  11. ↑ "Performance Tuning WCF Services, Caching". MSDN Library. Microsoft. Retrieved 14 February 2013.
  12. ↑ "Output Cache Provider (AppFabric 1.1 Caching)". MSDN Library. Microsoft. Retrieved 14 February 2013.
  13. ↑ "Developing a Cache Client". MSDN Library. Microsoft. Retrieved 14 February 2013.
  14. ↑ "Microsoft Delivers Release Candidate of Windows Server AppFabric, Beta Release of BizTalk Server 2010". Microsoft News Center. Microsoft. Retrieved 13 February 2013.
  15. ↑ "Introducing AppFabric 1.1". MSDN Library. Microsoft. Retrieved 13 February 2013.
  16. ↑ "Cumulative update package 1 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 15 February 2013.
  17. ↑ "Cumulative update package 2 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 15 February 2013.
  18. ↑ "Cumulative update package 3 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 15 February 2013.
  19. ↑ "Cumulative update package 4 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 16 April 2013.
  20. ↑ "Cumulative update package 5 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 7 October 2014.
  21. ↑ "Cumulative update package 6 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 1 May 2015.
  22. ↑ "Cumulative update package 7 for Microsoft AppFabric 1.1 for Windows Server". Microsoft Support. Microsoft. Retrieved 29 March 2016.
  23. ↑ "Microsoft announces End of Support". MSDN Blogs. Microsoft. Retrieved 2 April 2015.
  24. ↑ "Extended support". MSDN Blogs. Microsoft. Retrieved 19 June 2015.

External links

.

This article is issued from Wikipedia - version of the Tuesday, March 29, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.