docs
cloud-dapr-demo
| docs | cloud-dapr-demo | |
|---|---|---|
| 7 | 1 | |
| 988 | 21 | |
| 0.0% | - | |
| 9.7 | 0.0 | |
| 6 days ago | over 1 year ago | |
| HTML | JavaScript | |
| Creative Commons Attribution 4.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
.NET Aspire is the best way to experiment with Dapr during local development
Dapr documentation
-
Picking an architecture
I agree with the general sentiment here that you should try to keep things simple as long as possible. In addition to that, try to use frameworks such as Dapr, that allow you to postpone certain architectural decisions. Since Dapr runs everywhere where Kubernetes runs, it doesn't really matter which cloud provider you pick. Also, when it comes to pub/sub brokers, state stores, or secret stores, when using Dapr components you can easily swap those out.
-
Mechanism for managing faulty consumer in asynchronous event broadcast in microservices / modular monolith
I'm mostly familiar with orchestration type sagas, and there I usually include retries when calling services and compensation actions in case calls completely fail. It really helps if you're using a framework, such as Dapr, to do most of the heavy lifting. You can apply resiliency policies to service calls and with the latest version, there's now a Workflow API to orchestrate your services.
-
Service Mesh Considerations
One other option that is worth mentioning is Dapr. Dapr is a microservices building block that developers can use to develop microservices. There is a bit of overlap between Dapr and service meshes and the Dapr team has done a good job of comparing the two here. The biggest takeaway when comparing the two is that Dapr does not provide traffic routing/splitting. So if you need these capabilities, then yes, you will need a service mesh.
-
Virtual Actors : Dapr vs Orleans
There was a similar issue with the code examples to get/set state, so I created a GitHub issue for them.
-
Image Recognition App using GoLang | Tensorflow | WasmEdge | Dapr | Docker
It is an Image Recognition Application made using Go Language, works on a Tensorflow model and it requires Dapr and WasmEdge runtime for execution.
-
Tech Talks: Building Event-Driven Apps with Dapr in Kubernetes
Dapr Docs
cloud-dapr-demo
-
Tech Talks: Building Event-Driven Apps with Dapr in Kubernetes
ksivamuthu / cloud-dapr-demo
What are some alternatives?
dapr-wasm - A template project to demonstrate how to run WebAssembly functions as sidecar microservices in dapr
CAP - Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
Orleans.CosmosDB - Orleans providers for Azure Cosmos DB
jaeger - CNCF Jaeger, a Distributed Tracing Platform
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
zipkin - Zipkin is a distributed tracing system
smi-spec - Service Mesh Interface
osm - Open Service Mesh (OSM) is a lightweight, extensible, cloud native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments.
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
envoy - Cloud-native high-performance edge/middle/service proxy