1

What is the justifications for the service fabric reliable collections. The team I am working with is replacing the stateful services with stateless and removing the state to a redis server. As far as I understood was service fabric should eliminate the unnecassary talk and be fast at solving issues. I guess the persistance state parameter in service fabric and the debugging is so hard that the team gave up on it.

How should we approach service fabric projects

PS

I still feel that SF is the way to go as It gives us the 1000 server Virtual Machine scale sets architecture.

4

1 回答 1

4

可靠的收藏品非常棒，如果

  • 您有需要持久化的数据
  • 跨多个节点的高可用性
  • 尽可能接近应用程序代码（因此速度极快）
  • 可以在一个节点中无缝更新并跨节点复制
  • 允许程序员轻松地使用字典和队列进行编程，而无需学习另一种缓存机制

如果需要上述所有功能，可靠的集合是一个绝妙的解决方案。单个点可以通过其他方式实现，但将所有点放在一起需要一些繁重的工作和思考/经验。

使所有服务无状态将使单个服务快速，但它们仍然需要读取和写入 redis，这是另一个需要维护和提供高可用性的可执行文件。

于 2017-07-05T20:43:14.847 回答