OM1 platform supports both ROS2 and Zenoh middleware, but they serve different use cases.
ROS2 brings production-grade maturity and rich feature sets—perfect if you're working with legacy systems, running advanced navigation stacks, or dealing with complex SLAM algorithms. The tradeoff: heavier computational overhead and bandwidth consumption.
Zenoh takes the opposite approach. It's built for speed and efficiency, stripping away unnecessary layers to deliver a lightweight, high-performance middleware stack. Think minimal latency, lower network footprint, and simpler deployment.
So which one? ROS2 if you need battle-tested reliability and sophisticated capabilities. Zenoh if you're optimizing for efficiency and real-time responsiveness. Many teams actually run both—it just depends on your architecture demands.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
12 Likes
Reward
12
6
Repost
Share
Comment
0/400
LayerZeroHero
· 11h ago
It has proven that the two protocol architectures are designed to serve different scenarios. The ROS2 architecture is mature and reliable, but it consumes resources. I would like to see actual test data comparing it with Zenoh, this low-latency solution.
View OriginalReply0
MerkleTreeHugger
· 11h ago
ROS2 production-grade reliability is indeed impressive, but I'm more interested in Zenoh's lightweight approach.
View OriginalReply0
PortfolioAlert
· 11h ago
The shortcomings of ROS2 really consume too many resources, and I truly love Zenoh's lightweight design.
View OriginalReply0
DaoTherapy
· 11h ago
Neither can run away, let's see what your architecture is made of.
View OriginalReply0
MidnightMEVeater
· 11h ago
Good morning everyone, ROS2 is just a middleman relying on old assets, while Zenoh is the real arbitrage opportunity. Lightweight solutions reduce gas costs, whereas heavy-duty schemes are just tipping miners.
View OriginalReply0
ResearchChadButBroke
· 11h ago
ROS2 has been using so many resources for so long, while Zenoh is so lightweight—why isn't anyone using it?
OM1 platform supports both ROS2 and Zenoh middleware, but they serve different use cases.
ROS2 brings production-grade maturity and rich feature sets—perfect if you're working with legacy systems, running advanced navigation stacks, or dealing with complex SLAM algorithms. The tradeoff: heavier computational overhead and bandwidth consumption.
Zenoh takes the opposite approach. It's built for speed and efficiency, stripping away unnecessary layers to deliver a lightweight, high-performance middleware stack. Think minimal latency, lower network footprint, and simpler deployment.
So which one? ROS2 if you need battle-tested reliability and sophisticated capabilities. Zenoh if you're optimizing for efficiency and real-time responsiveness. Many teams actually run both—it just depends on your architecture demands.