<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Control planes | Keystone</title><link>https://carlosprados.github.io/keystone/control-planes/index.html</link><description>Three ways to drive the same agent. They are adapters over one shared CommandHandler, so any of them can do anything the others can — no feature drifts between transports.
Adapter Best for On by default HTTP Local management, debugging, Prometheus yes (loopback) MQTT IoT platforms, constrained devices, existing brokers no You can run several at once — HTTP on loopback for local debugging while MQTT carries fleet commands is a common combination:</description><generator>Hugo</generator><language>en</language><atom:link href="https://carlosprados.github.io/keystone/control-planes/index.xml" rel="self" type="application/rss+xml"/><item><title>HTTP</title><link>https://carlosprados.github.io/keystone/control-planes/http/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://carlosprados.github.io/keystone/control-planes/http/index.html</guid><description>The REST API, endpoint by endpoint.</description></item><item><title>MQTT</title><link>https://carlosprados.github.io/keystone/control-planes/mqtt/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://carlosprados.github.io/keystone/control-planes/mqtt/index.html</guid><description>Topics, QoS, and last-will for presence.</description></item></channel></rss>