dapr VS MassTransit

I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.

Just heard about Dapr last week. Might be more than what you are asking, though but it’s probably worth a look.

https://dapr.io/

From my perspective, I’d like to explore further how Dapr can integrate with other Supabase features. It would also be great to see a Supabase state store as a built-in component that’s available in the Dapr runtime without the need of running the pluggable component separately. I also hope the proposed DocumentStore building block will get some traction this year, since this will pair up very nicely with Supabase and other PostgreSQL stores.

Could you use Kubernetes to solve this? Have a single pod running the Redis instance and then multiple running Node.js talking to the Redis instance via something like DAPR (https://dapr.io/)

Dapr is also building a workflow orchestrator into their microservice system. It's almost in Beta, and when you combine it with Dapr's Virtual Actors, it looks powerful. It will also let you integrate a workflow engine like Temporal, too. https://dapr.io/

This fantastic blog from Mauricio (Salaboy) Salatino shows how tools like Kratix (kratix.io) and Dapr (dapr.io) can help streamline golden paths: https://blog.dapr.io/posts/2023/04/02/creating-dapr-enabled-platforms-with-kratix/

Recently, the Dapr maintainers released V1.10 of Distributed Application Runtime (Dapr), a developer framework for building cloud-native applications, making it easier to run multiple microservices on Kubernetes and interact with external state stores/databases, secret stores, pub/sub-brokers, and other cloud services and self-hosted solutions.

Dapr, the open-source distributed application runtime, is often used in event-driven applications. Dapr provides a set of standardized API building blocks that simplify microservice development. By using the Bindings building block, developers can use input, and output bindings, and either trigger their apps or invoke other resources without having to learn resource-specific SDKs for these resources. With Dapr release 1.10, a new binding is provided that allows developers to publish messages to Cloudflare Queues. Because of the common set of APIs that Dapr offers, developers from any background can use the binding to publish messages to Cloudflare Queues without needing to know the Cloudflare SDKs or adding that dependency to their codebase.

What would be the benefits of using your library instead of something like MassTransit?

However, I found this discussion on MT github: https://github.com/MassTransit/MassTransit/discussions/2546

MassTransit (https://github.com/MassTransit/MassTransit)

I really like https://masstransit-project.com/. I use it with both RabbitMQ and Azure Service Bus

There are many libraries in .NET that helps you implementing the outbox pattern like: MassTransit, NServiceBus, CAP. Talking about idempotency, a special mention to a specific lib from a big friend that runs on top of CAP which is called Ziggurat.

I actually found the MassTransit samples really enlightening. https://masstransit-project.com/

Look into IHostedService or use something like MassTransit

An example of a well architected system, that happens to align with a number of the guidelines from "Clean Architecture", imo, is MassTransit and (most) sibling projects.