<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>grpc on toorun.dev</title><link>https://toorun.dev/tags/grpc/</link><description>Recent content in grpc on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/grpc/index.xml" rel="self" type="application/rss+xml"/><item><title>D-Bus vs gRPC vs MQTT: A Practical Guide to Choosing the Right Communication Pattern</title><link>https://toorun.dev/posts/dbus-vs-grpc-vs-mqtt-practical-guide/</link><pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate><guid>https://toorun.dev/posts/dbus-vs-grpc-vs-mqtt-practical-guide/</guid><description>D-Bus vs gRPC vs MQTT: A Practical Guide to Choosing the Right Communication Pattern An embedded Linux device may need to pass a command between two local services, expose an API to a backend, and stream sensor readings to a fleet platform. D-Bus, gRPC, and MQTT can all move information, but they solve different communication problems.
The short version:
Use D-Bus for structured communication between processes on the same Linux machine.</description></item></channel></rss>