Handle Command
Subscribe to and handle incoming commands with business logic
Overview
A command handler is the receiving side of KubeMQ's Commands pattern — the code that actually does the work a caller is blocked waiting on. Instead of building your own request-routing layer on top of a queue, you register a handler once with SubscribeToCommands, and KubeMQ delivers every matching command on that channel to it as a long-lived, server-streamed subscription, turning the channel into a synchronous RPC endpoint.
Handling happens inside the callback passed to SubscribeToCommands: you read the command's id, body, and metadata, run your business logic, then build a reply with CommandReply::Builder().SetRequestId(cmd.id).SetResponseTo(cmd.response_to).SetExecuted(true) and send it with SendCommandResponse(). Copying id and response_to from the received command is what lets the broker correlate the reply back to the exact caller blocked on SendCommand — nothing else identifies which request the response belongs to.
Gotchas: the reply must reach the broker before the caller's SetTimeout deadline or the caller sees a timeout even if you eventually respond; the callback runs on a background thread, so slow or blocking business logic head-of-line blocks the next command; and both CommandReply::Builder().Build() and SendCommandResponse() return a status you must check — a silently dropped error leaves the caller waiting until it times out.
Prerequisites
- KubeMQ server running on
localhost:50000 - C++ SDK installed (vcpkg or CMake FetchContent)
- C++17 compiler (GCC 9+, Clang 9+, MSVC 2019+)
Code
// Example: commands/handle_command
//
// Demonstrates subscribing to commands and handling them with business logic.
// The handler processes incoming commands and sends back responses,
// logging all fields (id, channel, metadata, body) for observability.
//
// Channel: cpp-commands.handle-command
// Client ID: cpp-commands-handle-command-client
//
// Run with a KubeMQ server on localhost:50000
// (see https://docs.kubemq.io/deploy).
#include <kubemq/kubemq.h>
#include <atomic>
#include <chrono>
#include <iostream>
#include <thread>
int main() {
std::cout << "[1] Connecting to localhost:50000" << std::endl;
kubemq::ClientOptions options;
options.set_address("localhost", 50000);
options.set_client_id("cpp-commands-handle-command-client");
auto client_result = kubemq::Client::Create(options);
if (!client_result.ok()) {
std::cerr << "[ERROR] Failed to create client: " << client_result.status().message()
<< std::endl;
return 1;
}
auto& client = *client_result;
std::string channel = "cpp-commands.handle-command";
std::atomic<bool> command_handled{false};
// Register a command handler that processes incoming commands
// and logs all fields for comprehensive observability.
std::cout << "[2] Subscribing to commands on channel " << channel << std::endl;
auto sub_result = client->SubscribeToCommands(
channel, "",
[&client, &command_handled](const kubemq::CommandReceive& cmd) {
std::cout << "[4] Handling command: id=" << cmd.id << " channel=" << cmd.channel
<< " body=" << cmd.body << " metadata=" << cmd.metadata << std::endl;
// Process the command (business logic goes here).
// Then send back a response.
auto now_epoch = std::chrono::duration_cast<std::chrono::seconds>(
std::chrono::system_clock::now().time_since_epoch())
.count();
auto reply_result = kubemq::CommandReply::Builder()
.SetRequestId(cmd.id)
.SetResponseTo(cmd.response_to)
.SetExecuted(true)
.SetExecutedAt(now_epoch)
.Build();
if (!reply_result.ok()) {
std::cerr << "[ERROR] Build reply: " << reply_result.status().message()
<< std::endl;
return;
}
auto send_status = client->SendCommandResponse(*reply_result);
if (!send_status.ok()) {
std::cerr << "[ERROR] SendCommandResponse: " << send_status.message() << std::endl;
return;
}
command_handled.store(true);
},
[](const kubemq::Status& err) {
std::cerr << "[ERROR] Handler error: " << err.message() << std::endl;
});
if (!sub_result.ok()) {
std::cerr << "[ERROR] SubscribeToCommands: " << sub_result.status().message() << std::endl;
return 1;
}
auto& sub = *sub_result;
// Allow subscription to fully establish before sending.
std::this_thread::sleep_for(std::chrono::milliseconds(300));
// Send a command to trigger the handler.
std::cout << "[3] Sending command to channel " << channel << std::endl;
auto cmd_result = kubemq::Command::Builder()
.SetChannel(channel)
.SetBody("process-order")
.SetMetadata("order-123")
.SetTimeout(std::chrono::seconds(10))
.Build();
if (!cmd_result.ok()) {
std::cerr << "[ERROR] Build command: " << cmd_result.status().message() << std::endl;
return 1;
}
auto resp_result = client->SendCommand(*cmd_result);
if (!resp_result.ok()) {
std::cerr << "[ERROR] SendCommand: " << resp_result.status().message() << std::endl;
return 1;
}
std::cout << "[5] Response: executed=" << std::boolalpha << resp_result->executed << std::endl;
// Wait for the handler to finish processing.
std::this_thread::sleep_for(std::chrono::seconds(1));
// Cancel the subscription explicitly.
// Note: The Subscription destructor also calls Cancel(), but explicit
// cleanup is shown here for clarity and to match Go's defer pattern.
sub->Cancel();
std::cout << "[6] Subscription cancelled" << std::endl;
auto close_status = client->Close();
if (!close_status.ok()) {
std::cerr << "[ERROR] Close failed: " << close_status.message() << std::endl;
return 1;
}
std::cout << "[7] Client closed" << std::endl;
return 0;
}How It Works
- Registers a command handler that logs all fields (id, channel, body, metadata).
- Processes the command and sends back a response with
SendCommandResponse(). - Uses
CommandReply::Builder()with request ID, response-to address, and execution status. - The handler runs in a callback thread -- keep processing fast to avoid timeouts.
Related
Was this page helpful?