by ciprian.jichici@genisoft.eu
28. December 2009 23:37
In the past two weeks I had the chance to talk to several architects and dev leads about Microsoft’s strategy for distributed software solutions. One thing that caught my attention was a bit of a recurring confusion related to the AppFabric concept, so I thought it would be a good thing to make a few remarks on the matter.
First of all, we’re dealing today with two distinct AppFabric “editions”: Windows Azure platform AppFabric and Windows Server AppFabric. And to much of some people’s surprise, they are dealing with slightly different things. The big and obvious difference is that one of them is a cloud technology while the other is an on-premise one.
Second, I really have a hard time understanding why on earth did Microsoft go on the path of using the same name for two (apparently) rather different sets of technologies. Somehow reminds me of the .NET Framework 3.0 which is not actually a new framework since it still runs on the 2.0 CLR :) Well…
Windows Azure platform AppFabric is the thing that we used to call “.NET Services” (remember it from all the slides?) and that helps developers connect services and apps in the cloud or on-premises. Two of the most important things that it provides are a Service Bus for connectivity and Access Control for federated authorization. You can learn more about this technology at http://msdn.microsoft.com/en-us/azure/netservices.aspx.
On the other hand, Windows Server AppFabric is what you get by driving Windows Server with high velocity through Dublin…. To be more specific, Windows Server AppFabric (Beta 1 is currently available) is the beta outcome of two technologies previously named “Velocity” and “Dublin”. “Velocity” was the name of the distributed caching technology while “Dublin” was the name of the WF and WCF services management one. Consequently, Windows Server AppFabric merges these technologies into a platform with three core capabilities: distributed caching, workflow management, and service management. You can learn more about this at http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx.
Since AppFabric (regardless whether it’s the cloud stuff or the on-premises one) is going to have a huge impact on the architecture of our distributed applications built on the Microsoft Application Platform, I’ll get back in the coming weeks with a more detailed analysis of the architectural challenges it tries to address.