Getting Started with Dapr Using SmartIDE: A Complete Guide to the Dapr‑Traffic‑Control Sample

Dapr (Distributed Application Runtime) is a Microsoft‑led open‑source cloud‑native project that quickly gained popularity, reaching over 17 000 GitHub stars within a year of its V1.0 release. It offers a sidecar‑based, language‑agnostic runtime for adding distributed capabilities to applications.

Major Chinese tech companies such as Tencent, Alibaba, and DingTalk have adopted Dapr in production, appreciating its non‑intrusive design that works across multi‑cloud and non‑cloud environments.

Compared with Spring Cloud and Istio, Dapr provides full‑stack multi‑language support and equal multi‑cloud compatibility while avoiding the heavyweight dependencies of Istio and the Java‑only focus of Spring Cloud.

The article showcases the Dapr‑Traffic‑Control sample, which simulates a speed‑camera system that calculates vehicle speed and issues fines. The sample consists of three business services (TrafficControlService, FineCollectionService, VehicleRegistrationService) and relies on six middleware components: Dapr runtime (1.7.4), Zipkin, Redis, Mosquitto (MQTT broker), Maildev, and RabbitMQ.

Using smartide start https://github.com/SmartIDE/sample-dapr-traffic-control , developers can launch a containerized development environment that already includes Docker, VS Code WebIDE, and all required middleware. The environment can be run locally, on a remote Docker host, or in a Kubernetes cluster with a single command.

Key commands demonstrated:

smartide start https://github.com/SmartIDE/sample-dapr-traffic-control

# Add remote Docker host

smartide host add <Docker‑host‑IP> --username <user> --password <pass>

# Start environment on remote host

smartide start --host <host‑id> https://github.com/SmartIDE/sample-dapr-traffic-control

After initializing Dapr with dapr init , developers can start the auxiliary services using the provided PowerShell scripts ( pwsh start-all.ps1 and pwsh start-selfhosted.ps1 ) and run the visual simulator with dotnet run .

Once all containers are running (verified via docker ps ), the application can be accessed at http://localhost:5000 (simulator) and http://localhost:4000 (mail‑dev). The entire workflow demonstrates how SmartIDE removes the need to manually install Docker, configure SSH tunnels, or manage individual container images, providing a consistent development experience across environments.

Finally, the article includes promotional information about SmartIDE (free, open‑source, multi‑IDE support) and links to its website, B‑Station channel, and source repositories.