select messagebus

[mlz960820]

The first question：V3.0 use redis or mqtt，difference？I need to make frequent calls between the two services, app-functions-sdk-go and device-modbus-go.
The second question: The app-functions-sdk-go requires frequent device status checks. Should it send RESTful or ModbusBus requests to device-modbus-go, directly access the core-data service, or integrate a Redis client within the app-functions-sdk-go to reduce network traffic with core-data?

[cloudxxx8]

I don't understand yoru first question. Redis pub/sub and MQTT are different type of message bus. What is the purpose of your frequent calls?

What is your device status in the second question, is it OperatingState?

[mlz960820]

First, the message bus supports Redis and MQTT. Which one should I choose?
Secondly, frequent calls between interfaces of two services—should RESTful or MessageBus be recommended?

[cloudxxx8]

For message bus, I recommend to use MQTT, because the Redis open source license is changed.
For the frequent calls, it depends on your use case and scenario. Unless you provide more detailed use cases, I cannot provide any suggestion.

[mlz960820]

对于消息总线，我建议使用 MQTT，因为 Redis 开源许可证已经更改。频繁调用的话，取决于你的使用场景和场景。除非你提供更详细的使用场景，否则我无法提供任何建议。

We currently provide two device SDK-go services: device-user-go and device-modbus-go. Device-modbus-go interfaces with PLC DI, while device-user-go is used for devices like fans and lighting equipment. Therefore, autoevent requires frequent calls to device-modbus-go.

[cloudxxx8]

If you use autoevent, app service can receive the EdgeX events automatically. You don't have to use REST call to retrieve data.