简体繁体 English

FIWARE：扩展物联网代理

[英]FIWARE: Scaling IoT Agents

原文 2019-05-02 10:15:52 9 1 fiware

If one had a large FIWARE IoT system with a smart city's worth of connected devices, how would the IoT Agents be scaled? 如果有一个拥有智能城市价值的连接设备的大型FIWARE物联网系统，那么物联网代理将如何扩展？

Would the IoT Agents share state with each other like the Context Brokers or is the recommended strategy to divide devices among the IoT Agents? 物联网代理会像上下文代理一样彼此共享状态，还是在物联网代理之间划分设备的推荐策略？

If it's the former, are there any recommendations on the number of devices per agent? 如果是前者，是否有关于每个代理的设备数量的建议？ If it's the latter, are there some settings for sharing state? 如果是后者，是否有一些共享状态的设置？

1 个解决方案

It is difficult to assign numbers as you suggest, as the correct architecture for your system will depend on the throughput needed, which in turn depends on the rate and latency of your devices. 由于系统的正确架构取决于所需的吞吐量，而后者又取决于设备的速率和延迟，因此很难按照您的建议分配数字。

As a general rule you should keep the architecture as simple as possible, only adding in sharding and duplication of resources you are unable to get throughput with a simpler architecture. 作为一般规则，您应该尽可能简化架构，只需添加资源的分片和重复，您就无法通过更简单的架构获得吞吐量。

You can find some scaling recipes and architectures for FIWARE on the Smart SDK GitHub. 您可以在Smart SDK GitHub上找到FIWARE的一些缩放配方和体系结构。