Introducing Windows Server AppFabric
Monday, May 24, 2010
I know some application developers who really enjoy creating general infrastructure for their apps. My guess is that these people would be happier working for a software vendor--they shouldn't be application developers. Developers who get paid to write applications should write application code, not infrastructure. Software that provides general-purpose support for application logic--operating systems, database systems, and much more--should be provided by vendors.
Windows Server AppFabric is an important example of this. By providing caching and hosting services for Windows applications, it can reduce the amount of general-purpose infrastructure that app developers must write. I've written a Microsoft-sponsored introduction to this technology, available here
, that provides a big-picture view of what it is and why you'd use it.
Don't confuse Windows Server
AppFabric with Windows Azure
AppFabric. Both have "AppFabric" in their names, and both provide infrastructure for applications, but they currently have no technologies in common. Microsoft tells us that this will change in the not-too-distant future, with the Windows Server AppFabric technologies appearing in Windows Azure AppFabric. You shouldn't let this throw you, though: the caching and hosting services of Windows Server AppFabric can be useful for Windows apps today.