我对 Appfabric 的替换 ASP.NET 会话管理器部分非常感兴趣，对分布式缓存管理器有些兴趣。我们不需要它的托管功能。虽然我们内部确实有一个集群 SQLServer，但将其添加为我们的 aspnet/oracle 应用程序的依赖项可能不会受到好评。
有一个基于网络的 XML 文件选项，appfabric 视频建议它适用于小型部署，我们将是（一个 2 节点农场，一个 5 节点农场）。
那么后端有没有没有 SQLServer 的成功案例呢？对于 Appfabric 而不是 SQLServer，DFS 网络共享是否足够可靠？
I think this is precisely the situation where the AppFabric team intended the XML provider to be used i.e. where SQL Server is not available/not desired. I doubt that there are any case studies available yet where this has been done, purely because AppFabric is so new that they haven't been written yet. However I don't believe there are any quirks to using the XML provider over the SQL provider - all I can suggest is try it and see! You could always switch over to SQL Server at a later date if the XML provider proves problematic. Or if you're felling brave, you should be able to write an Oracle provider (though the documentation on this seems, um, sketchy).