Using gRPC as a IoT protocol instead of LWM2M/CoAP

[ale...@gmail.com]

The rpc interface specification in Protocol Buffer (ver 3) along with the efficient implementation via gRPC is leading me to choose this over CoAP/ LWM2M (Leshan Java and Wakaama C++ implementation). Having used both gRPC is developer friendly and development , interface definition is fast,compared to OMA LWM2M process; Of course there is no Observer-Notify in gRPC, but for that MQTT should suffice. LWM2M is not just the inteface but defines behaviour in lot of IoT cases like BootStrap, Registration, KeepAlive , SW Upgrade etc and its universal HTTP like GET, PUT on an URL type addressable resource makes it very complete. However most of these behaviours can be custom defined with some effort. Some of the IoT things which we plan to orchestrate are far from little brained devices like bulbs, and more like robots. Any thoughts or comments could help.

[Vijay Pai]

Although there has been some gRPC IoT work, I don't think that any team members have expertise in the technologies that you've described. Maybe you can get an answer on this forum from a community member, or perhaps on another forum like StackOverflow?

Best regards,

Vijay