Integration / D Bus Interview Questions
What is the difference between D-Bus and gRPC for IPC?
D-Bus and gRPC solve overlapping problems, letting separate processes call into each other, but they come from different design centers and fit different environments.
| D-Bus | gRPC |
| Local IPC via a bus daemon and Unix sockets | Designed for networked services, typically over HTTP/2 |
| Broadcast signals to multiple subscribers natively | No native broadcast; typically point-to-point or server-streaming |
| Runtime introspection built into the protocol | Contracts defined ahead of time via .proto files |
| Deeply embedded in the Linux desktop/system stack | Language-agnostic, widely used across distributed backend services |
D-Bus is the natural choice for coordinating processes on a single Linux machine that need discovery, broadcast signals, and deep integration with existing system services like systemd or NetworkManager. gRPC is the natural choice for structured, high-performance calls between services that might run on different machines, where strongly typed, code-generated contracts and standard network transport matter more than desktop-level integration.
A key structural difference is that D-Bus natively supports:
gRPC is generally the better fit when:
More Related questions...
