docs
dapr-wasm
| docs | dapr-wasm | |
|---|---|---|
| 7 | 4 | |
| 988 | 263 | |
| 0.0% | 0.0% | |
| 9.7 | 5.8 | |
| 7 days ago | 6 months ago | |
| HTML | Rust | |
| Creative Commons Attribution 4.0 | Apache License 2.0 |
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
dapr-wasm
-
Rust microservices in server-side WebAssembly
The Dapr SDK for WASI (WebAssembly System Interface) enables WasmEdge-based microservices to access their attached Dapr sidecars. A complete demo application with a Jamstack static web frontend, three microservices, and a database service is also available.
-
Lightweight Dapr Microservices in WebAssembly
Dapr is a very popular sidecar-based application framework that supports microservices written in many languages. WasmEdge is a cloud-native WebAssembly runtime. It provides the necessary networking APIs to support WebAssembly-based microservices.
Learn how to create Rust and JavaScript functions, and run them as Dapr microservices through the WasmEdge runtime? How to interact with Dapr APIs from the WebAssembly function and how to manage the WadmEdge microservices using Kubernetes? Source code and a live example are available here: https://github.com/second-state/dapr-wasm
-
Image Recognition App using GoLang | Tensorflow | WasmEdge | Dapr | Docker
git clone https://github.com/second-state/dapr-wasm.git
-
Running JavaScript in WebAssembly with WasmEdge
Runtime for sidecar applications in a service mesh
What are some alternatives?
CAP - Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
SSVM - WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.
Orleans.CosmosDB - Orleans providers for Azure Cosmos DB
awesome-dapr - A cruated list of awesome Dapr application runtime related tools.
jaeger - CNCF Jaeger, a Distributed Tracing Platform
aws-lambda-wasm-runtime - A template project for building high-performance, portable, and safe serverless functions in AWS Lambda.
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
layotto - A fast and efficient cloud native application runtime
cloud-dapr-demo - Demo of Dapr runtime and seamless integration of cloud providers
wasmedge-quickjs - A high-performance, secure, extensible, and OCI-complaint JavaScript runtime for WasmEdge.
zipkin - Zipkin is a distributed tracing system
tencent-scf-wasm-runtime - 基于 WebAssembly 容器镜像的高性能腾讯云函数开发模版。A template project for building high-performance, portable, and safe serverless functions in Tencent Serverless Cloud Functions.