Part
Middleware
You might say: ROS 2, message passing
Middleware lets independent programs exchange typed messages and invoke services or actions over named interfaces.
- What it does
- It separates components so teams can replace, inspect and deploy them independently.
- Ask
- What message type, QoS, latency and update rate does each interface need?
Catalogue: Middleware
- ROS 2: ROS 2 uses nodes and typed topics, services and actions; DDS-backed QoS can tune reliability, durability and deadlines.
- ROS 1: ROS 1 Noetic was marked end-of-life on 31 May 2025.
- In-house framework: A project-owned framework can use a custom in-house binary format instead of ROS.
Sources
- Morgan Quigley, Brian Gerkey and William D. Smart, Programming Robots with ROS: A Practical Introduction to the Robot Operating System, Preface, distributed messages
connect to one another and continuously exchange messages
Use it on your project
teardown-apply: hold "Middleware" (middleware) from the teardown at https://teardownatlas.com/robotics/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal