App Fabrics are Microsoft Products, there are designed specially to elevate and to better consume the IT infrastructure. The App Fabrics come in 2 flavors one designed for the Windows Server and the second one is for the Cloud Computing platform for Microsoft Windows Azure, however the name of App Fabrics is no longer in use for the Windows Azure and all its components are now independent services that you can consume for your application. In this blog post I will write a small introduction about each one of them.
But first let’s see the Windows Server App Fabrics, to learn more and to develop using the App Fabrics you can check these labs and download its samples from here. The two main features of the Windows Server App Fabrics are the Caching Services and the second one is for managing the hosted services on your server. You can enhance the hosted services using both the WCF (Windows Communication Foundation) and the WF (Workflow Foundation).
I will make a small introduction about each feature of the App Fabric for Windows Server for more information you can read the post related to it. For the Caching Service, like the normal PC works the cache is a temporary memory that helps memory used by the processor. The Caching Service is a little bit the same but runs for a cluster. Certainly it is not that simple, it is more complicated than that for maintaining the High Availability of the application. All about the Caching Service you can find it here.
Second the managing hosted services, is a simple explanation about it, you can consider it like the Workflow, a better way for developing your application along the infrastructure.
For Windows Azure, it had a lot of services other than the processing and storage. They were grouped under the name of App Fabrics but now each service is named with its name, for example the service bus, the access control, caching, Integration and Composite app. There are some of them still under development.
Like the Windows Server App Fabrics features, I will simply introduce each feature and will write a post about each one. For the Service Bus, it is a relay service that mainly made for enhancing the way of connectivity between two different applications no matter where they are hosted and even if one of them is hosted behind a firewall. Here is the link for the full explanation of the Service Bus.
For the Access Control, it is a service basically based on Service Bus that also is made for enhancing the connectivity between the application, the client and the third party, mainly designed for authentication and authorization from different third parties, like Hotmail, Facebook, Google and others.
The third service is the caching service, like for Windows Server Caching Service, the Windows Azure Caching is mainly designed for a better scalable and high performance application storage services as the Windows Azure storage and SQL Azure. There are some features in the Caching that is still under development.