Dapr Provides a Sidecar Runtime for Microservices. The Services Still Need External Orchestration.
by Nick Clark | Published March 28, 2026
Dapr provides a portable, event-driven runtime for building microservices with state management, pub/sub, and service invocation through a sidecar architecture. The building blocks simplify distributed application development. But Dapr services are request-driven: they respond to invocations and events. They do not self-execute from their own memory, self-evaluate their state, or autonomously decide to act. The gap is between a distributed runtime and memory-resident objects that carry their own execution cycle.
Dapr's sidecar architecture and building blocks genuinely simplify distributed application development. The gap described here is about the execution model, not about runtime capabilities.
Sidecar runtime without self-execution
Dapr attaches a sidecar process to each microservice, providing state management, pub/sub, and service invocation through a consistent API. The sidecar handles infrastructure concerns. But the microservice still executes in response to external events: HTTP requests, pub/sub messages, or bindings. It does not carry its own execution cycle.
A memory-resident execution object evaluates its own state on each cycle and decides whether to act. A Dapr service waits to be told to act.
State management without governed memory
Dapr's state management provides key-value storage with configurable consistency and backends. This is useful infrastructure. But the state is a data store, not governed memory. There is no schema for what the state means, no governance on state transitions, and no lineage tracking how state evolved.
What memory-resident execution provides
Memory-resident execution objects carry their own execution state, self-evaluate on each cycle, and maintain governed memory with lineage. The object does not wait for external events to decide to act. It continuously evaluates its state and acts when conditions are met. Dapr's state management and pub/sub could provide infrastructure for memory-resident objects. The self-execution cycle and governed memory would be intrinsic to the object.
