AppFabric 作为状态服务器的速度
有人使用 Windows AppFabric Server 进行进程外状态管理吗？
任何反馈、建议将不胜感激。
Is anybody using Windows AppFabric Server for out of process state management?
Any feedback, advice would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用 AppFabric 缓存。我们尝试了这个，它似乎有效，易于设置等。在设置有关持久性的缓存时，有一些非常奇怪的设置，需要仔细阅读。
我们的问题是在两台服务器上安装了 IIS 和 Appfabric Caching，并告诉应用程序首先尝试本地服务器。当我们刚投入生产时就开始失败。看起来只有两台服务器，有一台主服务器，如果它出现故障，一切都会停止工作，我们读到，如果需要扩展到 3 台或更多服务器以获得我们想要的行为。当刚刚上线且无法工作时，这不是一个选择，因此我们暂时切换到 SQL Server，同时我们查看 nCache、ScaleOut 和 Memchached
另一个问题是缓存和会话状态不是同一个动物，如果您丢失了缓存，则不应该这样做世界末日只是将其重新组合在一起，我们需要不惜一切代价在指定的时间段内保持会话状态。
Using AppFabric Caching. We tried this and it appeared to work, was easy to setup etc. There are some very strange settings when setting up the cache about peristance which need to be read carefully.
Our issue was on two server we installed IIS and Appfabric Caching and told app to try the local one first. When we went into production is just started to fail. It appears that with only two servers there is a lead server which if it goes down things stop working, we read that if needed to scale to 3 or more servers to get the behaviour we wanted. Not an option when just gone live and not working so we switched to SQL server for now while we look at nCache and ScaleOut and Memchached
The other issue is that caching and session state are not the same animal, if you loose your cache it should not be the end of the world just put it back together, we need to keep session state for the lotted time period at all costs.