Click here to Skip to main content
15,881,757 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
Hi,

I'm in the infrastructure planning phase of a nice new green field project.

Oh how I love green field projects... The opportunity to adopt something new from the endless development technologies in the market place.

I've spent the afternoon reading white papers and the MSDN content on AppFabric (Code name Velocity & Dublin).

If I run a workflow service (WCF and WF in a service) upon AppFabric. It seems to do a lot of the things I've previously had to develop using my own independent infrastructure layer. Such as long term state persistence, non-sticky sessions, improve start up speed, improved data request speeds e.t.c.

So I know why I should use AppFabric. Can anyone tell me why I shouldn't use it? What are the pitfalls? What problems have the development community run into when using it?

Or perhaps you can suggest and alternate infrastructure framework that would accelerate development more effectively than AppFabric would?
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900