ros2-service-pattern

To create a ROS 2 service server and client example for education, use the AddTwoInts pattern from example_interfaces.srv in ROS 2 Humble. It generates canonical synchronous server callbacks and asynchronous clients using rclpy to teach inter-node communication.

ROS 2 services differ from topics by using a request/response pattern instead of continuous data streaming. Services are suitable for immediate, synchronous or asynchronous tasks like AddTwoInts, whereas topics are better for continuous sensor data streams in robotics education.

An asynchronous ROS 2 service client handles responses using the call_async method in rclpy. This non-blocking pattern sends requests without halting node execution and processes the returned future result once the server completes its callback.

Yes, you can use the AddTwoInts service example with ROS 2 Humble. The generated code strictly enforces canonical ROS 2 patterns and aligns with official Humble tutorials to ensure compatibility and educational accuracy for inter-node communication lessons.

The best way to teach ROS 2 request and response patterns is by generating reproducible server and client code examples. Using the AddTwoInts interface demonstrates synchronous server callbacks and asynchronous clients, providing a clear comparison against topic-based communication.