How would you describe the Windows Azure AppFabric?
I was reading through the FAQ document for the Windows Azure platform this evening (what else is there to do on a Sunday night?), and I came across the following:
What is the Windows Azure AppFabric?
With AppFabric, Microsoft is delivering services that enable developers to build and manage composite applications more easily for both server and cloud environments. Windows Azure AppFabric, formerly called “.NET Services”, provides cloud-based services that help developers connect applications and services across Windows Azure, Windows Server and a number of other platforms. Today, it includes Service Bus and Access Control capabilities. Windows Server AppFabric includes caching capabilities and workflow and service management capabilities for applications that run on-premises.
Windows Azure AppFabric is built on Windows Azure, and provides secure connectivity and access control for customers with the need to integrate cloud services with on-premises systems, to perform business-to-business integration or to connect to remote devices.
The Service Bus enables secure connectivity between services and applications across firewall or network boundaries, using a variety of communication patterns. The Access Control Service provides federated, claims-based access control for REST web services. Developers can use these services to build distributed or composite applications and services.
I’ve spent a lot of time with the AppFabric, and believe I understand the intent of the above description. But what about the rest of you? If you have, or even if you haven’t, spent time using the AppFabric, how does this description resonate? Does this help you understand the AppFabric, or are you left confused? Do you understand it’s place and value in the larger Windows Azure platform?
I implore you to leave some feedback and let me know what you think. Please, share your thoughts! How can this be improved?
Wade Wegner works for Microsoft and is the Technical Evangelist for Windows Azure AppFabric.
[...] This post was mentioned on Twitter by Wade Wegner and others. Wade Wegner said: How would you describe the Windows Azure AppFabric? Please, I want to hear from you – http://bit.ly/bRibKi #azure #appfabric [...]
AppFabric looks nice on paper, but it is too bulky to my taste, mixing concepts of Request/Reply development with message-based development.
I found it to be simpler (for me) to develop (and open source) Azure App Engine for building scalable cloud applications, than work with AppFabric.
Rinat, what exactly is “Azure App Engine”?
It’s certainly wordy, but I feel that the text accurately describes where Azure App Fabric is today. What I don’t see portrayed very well is where it is going. How does it relate to SQL Server App Fabric? I believe that Microsoft will have a compelling story one day, but right now App Fabric seems to be just a brand name paited on to some disparate tools.
Good feedback, Michael. So, in addition to defining AppFabric today, it should do a better job of defining exactly where AppFabric fits in the larger context?
Wade,
“Azure App Engine” is just an Open Source Lokad.CQRS App Engine running within Windows Azure Worker Role, while taking advantage of features provided by the Fabric.