mchmarny/dapr-demos

Collection of personal Dapr demos (bindings, state, pub/sub, service-to-service invocation)

Dapr demos

Collection of personal Dapr demos.

Note, some of these demos require latest version of Dapr, Ingress gateway, Observability components, or cluster-local Redis and Mongo services. To create Kubernetes cluster with all these components on AKS, or quickly configure an existing cluster, consider the Dapr Cluster Setup utility.

• Bindings
  • Scheduling using cron - Using scheduler to execute service
  • Tweet stream - Subscribing to a Twitter even stream and publishing to a pub/sub topic
  • State change handler - RethinkDB state changes streamed into topic
• Eventing
  • gRPC event subscriber - Subscribing to topic and processing its events using gRPC service
  • HTTP event subscriber - Subscribing to topic and processing its events using HTTP service
• Services
  • gRPC echo service - gRPC service invocation example
  • HTTP echo service - HTTP service invocation example
  • Sentiment Scorer - Sentiment scoring serving backed by Azure Cognitive Service
• Integrations
  • Components in ACI - Dapr components as microservices on ACI without app
  • Component in Kubernetes - Dapr components as microservices on Kubernetes without app
  • Dapr Apps in ACI - Deploying apps with Dapr sidecar and components on ACI
  • Dapr with APIM - Dapr API using Azure API Management self-hosted gateway
  • Dapr API on Ingress - Expose Dapr API on Kubernetes Ingress Controller using NGINX
  • Dapr GitOps - GitHub Actions build pipeline for Dapr apps
• Solutions
  • Order cancellation - multiple Dapr service integrations with observability
  • Pipeline - Demos combining Twitter binding, Sentiment scoring, Multi Pub/Sub Processor, and WebSocket Viewer app
  • Fan-out - Single message source "broadcasted" to multiple, configurable targets (e.g. Redis PubSub, HTTP, gRPC)
  • Hardened - Example of multi-microservice app with tightly controlled access to secrets, components, and full invoking service identity validation
• Templates
  • Dapr gRPC Service - gRPC service template
  • Dapr HTTP Event Subscriber - Event subscriber HTTP service template
  • Dapr gRPC Event Subscriber - Event subscriber gRPC service template
  • dapr-http-cron-handler - Scheduled service development template

Disclaimer

This is my personal project and it does not represent my employer. While I do my best to ensure that everything works, I take no responsibility for issues caused by this code.

License

This software is released under the MIT

dapr-demos's Issues

Update order-cancellation to Dapr v0.10 API

keda scale up doesn't work despite large queue length lag

Example log

{"level":"debug","ts":1598799261.2208235,"logger":"kafka_scaler","msg":"Group autoscaling has a lag of 147410 for topic messages and partition 0\n"}
{"level":"debug","ts":1598799261.2208657,"logger":"scalehandler","msg":"Scaler for scaledObject is active","ScaledObject.Namespace":"default","ScaledObject.Name":"queue-outoscaling-scaler","ScaledObject.ScaleType":"deployment","Scaler":{}}
{"level":"debug","ts":1598799261.2310224,"logger":"scalehandler","msg":"ScaledObject's Status was properly updated","ScaledObject.Namespace":"default","ScaledObject.Name":"queue-outoscaling-scaler","ScaledObject.ScaleType":"deployment"}

This seems to be an issue with the HPA config (i.e. too old resource version)

W0830 14:54:22.057920       1 reflector.go:289] pkg/mod/k8s.io/[email protected]+incompatible/tools/cache/reflector.go:94: watch of *unstructured.Unstructured ended with: too old resource version: 1894736 (1894804)

There is a similar HPA issue being reported here

About "fan-out" demo

Should a config folder be under the "dapr-demos/fan-out/grpc-echo-service/" ? Thanks

Problem with grpc-echo-service

Hello, I am trying to complete the dapr-apim-integration demo, which depends on the grpc-echo-service docker image that you own.

When I run the demo as is, I get the error PostStartHookError: command '/daprd --wait' exited with 137

I have tried pulling the code for the image as you have defined in this repo (which appears more up-to-date than that in the quickstart docs) and building and deploying that I get the same error. Do you know why this may be?

Sorry if this isn't a real issue, just kinda puzzled and figured the original author might have more context than I do about the daprd process/error codes.

demo multi-tenant (non-hostile) Dapr deployment

• namespace per app
• shared data service
• app-stopped components
• scoped service invocations
• consolidated ingress

Update dapr-pipeline to Dapr v0.10 API

Update setup to Dapr v0.10

add twitter query with sentiment invoke example

keda scale up doesn't work despite large queue length lag

Example log

{"level":"debug","ts":1598799261.2208235,"logger":"kafka_scaler","msg":"Group autoscaling has a lag of 147410 for topic messages and partition 0\n"}
{"level":"debug","ts":1598799261.2208657,"logger":"scalehandler","msg":"Scaler for scaledObject is active","ScaledObject.Namespace":"default","ScaledObject.Name":"queue-outoscaling-scaler","ScaledObject.ScaleType":"deployment","Scaler":{}}
{"level":"debug","ts":1598799261.2310224,"logger":"scalehandler","msg":"ScaledObject's Status was properly updated","ScaledObject.Namespace":"default","ScaledObject.Name":"queue-outoscaling-scaler","ScaledObject.ScaleType":"deployment"}

This seems to be an issue with the HPA config (i.e. too old resource version)

W0830 14:54:22.057920       1 reflector.go:289] pkg/mod/k8s.io/[email protected]+incompatible/tools/cache/reflector.go:94: watch of *unstructured.Unstructured ended with: too old resource version: 1894736 (1894804)

There is a similar HPA issue being reported here

Dapr Helm deployment with tag errs on RC

After deploying Dapr using Helm

helm install dapr dapr/dapr -n dapr-system \
		--set global.tag=1.0.0-rc.1 \
		--set global.logAsJson=true \
		--set global.ha.enabled=true

On deployments with dapr enabled annotations, the deployment or replica set fails on start

message: 'admission webhook "sidecar-injector.dapr.io" denied the request: invalid
app id: a lowercase RFC 1123 label must consist of lower case alphanumeric characters
or ''-'', and must start and end with an alphanumeric character (e.g. ''my-name'',  or
''123-abc'', regex used for validation is ''[a-z0-9]([-a-z0-9]*[a-z0-9])?'')'

Applying deployment/kafka-pubsub.yaml with a specification validation error

Hi, I'm experimenting with the autoscaling-on-queue example and I got the following error when I got to step Deployment

~# kubectl apply -f deployment/kafka-pubsub.yaml

error: error validating "deployment/kafka-pubsub.yaml": error validating data: ValidationError(Component.spec): missing required field "version" in io.dapr.v1alpha1.Component.spec; if you choose to ignore these errors, turn validation off with --validate=false

Should it be changed to this?

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: autoscaling-pubsub
spec:
  version: v1
  type: pubsub.kafka
  metadata:
    - name: brokers
      value: kafka-cp-kafka.kafka.svc.cluster.local:9092
    - name: authRequired
      value: "false"
    - name: allowedTopics
      value: metric
    - name: consumerID
      value: autoscaling-subscriber

thk.

add ns creation w/ zipken, data secrets