Dapr integration overview in Azure - Commands & Configuration

Introduction

Dapr helps apps talk to each other and use cloud features easily. It solves the problem of writing complex code to connect services by providing simple building blocks.

When you want your app to save state without writing database code.

When your app needs to send messages to other apps reliably.

When you want to call another service without worrying about network details.

When you want to run your app on Azure and use cloud features simply.

When you want to add features like pub/sub or secrets without changing your app much.

Config File - dapr-config.yaml

dapr-config.yaml

apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: appconfig
spec:
  tracing:
    samplingRate: "1"
  mtls:
    enabled: true
  httpPipeline:
    handlers:
    - name: cors
      type: middleware.http.cors
      version: v1
      metadata:
      - name: allowedOrigins
        value: "*"
  features:
  - name: actors
    enabled: true

This file configures Dapr features for your app.

• tracing: Enables tracing to see app calls.
• mtls: Secures communication between services.
• httpPipeline: Adds middleware like CORS for web requests.
• features: Enables actors for stateful services.

Commands

This command installs and starts Dapr runtime locally on your machine to test apps with Dapr features.

Terminal

dapr init

Expected Output

Downloading binaries and setting up Dapr runtime...

Dapr has been successfully initialized

Starts your app with Dapr sidecar. The sidecar listens on port 3500 and your app runs on port 5000. This lets your app use Dapr features via HTTP calls to the sidecar.

Terminal

dapr run --app-id myapp --app-port 5000 --dapr-http-port 3500 dotnet run

Expected Output

== APP == Now listening on: http://localhost:5000

== DAPR == Starting Dapr sidecar on HTTP port 3500

→

--app-id - Sets a unique name for your app in Dapr

→

--app-port - Specifies the port your app listens on

→

--dapr-http-port - Sets the port for Dapr sidecar HTTP API

This command asks Dapr sidecar to get state stored under 'mykey' from the configured state store. It shows how your app can use Dapr to save and retrieve data easily.

Terminal

curl http://localhost:3500/v1.0/state/statestore/mykey -X GET

Expected Output

"myvalue"

Key Concept

If you remember nothing else, remember: Dapr runs alongside your app as a helper that makes cloud features easy to use without changing your app code much.

Common Mistakes

Not running 'dapr init' before starting the app with Dapr.

Dapr runtime is not installed or started, so the sidecar cannot run and your app won't connect to Dapr features.

Always run 'dapr init' once before running apps with Dapr.

Using wrong ports or missing --app-port when running 'dapr run'.

Dapr sidecar cannot forward calls to your app if ports are incorrect, causing communication failures.

Specify correct --app-port matching your app's listening port.

Calling Dapr APIs directly on app port instead of Dapr sidecar port.

Dapr APIs are exposed on the sidecar port, not your app port, so calls fail or get no response.

Use the Dapr HTTP port (default 3500) to call Dapr APIs.

Summary

Run 'dapr init' to install and start Dapr runtime locally.

Use 'dapr run' with your app to start it alongside the Dapr sidecar.

Call Dapr APIs on the sidecar port to use features like state management.

Practice

1. What is the main purpose of Dapr in cloud applications?

easy

A. To replace cloud providers completely

B. To simplify cloud app features without complex code

C. To create virtual machines automatically

D. To manage user interface design

Solution

1. Step 1: Understand Dapr's role

   Dapr helps developers by making common cloud app features easy to use without writing complex code.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks. Only To simplify cloud app features without complex code matches Dapr's purpose.

3. Final Answer:

   To simplify cloud app features without complex code -> Option B

4. Quick Check:

   Dapr simplifies cloud features = A [OK]

Hint: Remember: Dapr eases cloud features, not replaces providers [OK]

Common Mistakes:

• Thinking Dapr replaces cloud providers
• Confusing Dapr with UI tools
• Assuming Dapr manages virtual machines

2. Which of the following is a valid Dapr configuration setting?

easy

A. samplingRate: 1

B. MaxInstances: 1000

C. AutoScale: off

D. UITheme: dark

Solution

1. Step 1: Identify common Dapr config options

   Dapr configuration often includes settings like tracing and security, e.g., samplingRate.

2. Step 2: Evaluate options

   Options A, B, and D are unrelated to Dapr's config. Only samplingRate: 1 is valid.

3. Final Answer:

   samplingRate: 1 -> Option A

4. Quick Check:

   Dapr config includes tracing = C [OK]

Hint: Look for tracing or security keywords in config [OK]

Common Mistakes:

• Choosing unrelated config keys
• Confusing Dapr config with app settings
• Selecting UI or scaling options not in Dapr

3. Given this Dapr component YAML snippet:

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: statestore
spec:
  type: state.azure.cosmosdb
  metadata:
  - name: url
    value: https://mycosmos.documents.azure.com:443/
  - name: masterKey
    value: secretkey
  - name: databaseName
    value: mydb

What does this configuration do?

medium

A. Defines a state store component using Azure Cosmos DB

B. Creates a new Cosmos DB database named 'mydb'

C. Sets up a message queue for app communication

D. Configures tracing for Dapr components

Solution

1. Step 1: Analyze the YAML kind and spec

   The kind 'Component' with type 'state.azure.cosmosdb' means it defines a state store using Cosmos DB.

2. Step 2: Understand metadata fields

   Metadata includes connection info (url, masterKey, databaseName) for Cosmos DB access, not creating DB or queues.

3. Final Answer:

   Defines a state store component using Azure Cosmos DB -> Option A

4. Quick Check:

   Component type state.azure.cosmosdb = D [OK]

Hint: Look for 'state.azure.cosmosdb' type to identify state store [OK]

Common Mistakes:

• Thinking it creates the database itself
• Confusing state store with message queue
• Assuming it configures tracing

4. You have this Dapr configuration snippet:

apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: myconfig
spec:
  tracing:
    samplingRate: "0.5"
  mtls:
    enabled: true

What is the error in this configuration?

medium

A. mtls cannot be enabled in Dapr configuration

B. metadata name must be 'default'

C. Missing component type field

D. samplingRate should be a number, not a string

Solution

1. Step 1: Check tracing samplingRate format

   samplingRate expects a numeric value, but "0.5" is a string (in quotes), which is invalid.

2. Step 2: Validate other fields

   mtls enabled is valid, component type is not required in Configuration kind, and metadata name can be custom.

3. Final Answer:

   samplingRate should be a number, not a string -> Option D

4. Quick Check:

   samplingRate type error = B [OK]

Hint: Check data types carefully in YAML values [OK]

Common Mistakes:

• Assuming mtls can't be enabled
• Expecting component type in Configuration
• Thinking metadata name must be 'default'

5. You want to secure communication between your microservices using Dapr. Which combination of settings should you configure?

hard

A. Only configure tracing to monitor traffic

B. Disable mTLS and increase component replicas

C. Enable mTLS in Dapr configuration and set tracing samplingRate

D. Use Dapr without any configuration changes

Solution

1. Step 1: Identify security features in Dapr

   Dapr supports mTLS (mutual TLS) to secure service-to-service communication.

2. Step 2: Combine security with observability

   Enabling mTLS secures communication; setting tracing samplingRate helps monitor traffic, both important.

3. Final Answer:

   Enable mTLS in Dapr configuration and set tracing samplingRate -> Option C

4. Quick Check:

   mTLS + tracing for secure, observable communication = A [OK]

Hint: Secure with mTLS and monitor with tracing [OK]

Common Mistakes:

• Disabling mTLS weakens security
• Ignoring tracing for observability
• Assuming no config needed for security