vonage-dotnet-sdk
MediatR
vonage-dotnet-sdk | MediatR | |
---|---|---|
2 | 53 | |
103 | 10,659 | |
-1.0% | - | |
9.6 | 5.9 | |
1 day ago | 17 days ago | |
C# | C# | |
Apache License 2.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.
vonage-dotnet-sdk
-
The Monad Invasion - Part 2: Monads in Action!
Previously, we built an Optional and showed an existing set based on Language-Ext, but various libraries also offer Monad implementations. In the case of our SDK, we deliberately avoided relying on external libraries like Language-Ext. Indeed, Monads are a part of the SDK's public API, and relying on an external library would introduce a dependency over which we would have limited control.
-
The Monad Invasion - Part 1: What's a Monad?
This is the first post in a series that aims to demystify Monads and help you benefit from them, using real-life examples from our .NET SDK. Watch my related talk "Throw exceptions... out of your codebase" which was more about Monads than it was about exceptions, even if the title says otherwise.
MediatR
-
The Monad Invasion - Part 2: Monads in Action!
You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).
-
How small is the smallest .NET Hello World binary?
The widely used MediatR library[0] could be used to do that as well, just FYI.
[0]: https://github.com/jbogard/MediatR
- Cannot use disposed service
- Exception handling between controller and service
-
CQRS: How to handle duplicate queries inside a CommandHandler
Hope this GH issue shed some light on why injecting handler inside another handler is not good https://github.com/jbogard/MediatR/issues/400
-
Is MediatR the only real CQRS solution for .Net?
From: https://github.com/jbogard/MediatR
-
Easiest way to build the fastest REST API in C# and .NET 7 using CQRS
I gave it a go and I was impressed how easy and fast it was to set it all up. Since I'm not a big fan of REPR pattern almost all my projects are using CQRS pattern with a help of MediatR ](https://github.com/jbogard/MediatR) I immediately started going over something similar that Fast Endpoints offer which is a command bus.
-
MVVM Question: How do you manage the interaction between Model and ViewModel?
I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.
-
Async Methods after setting a property.
If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.
-
I don't get why I should use Redux
What people really want is to design the logic of an app independently from the component hierarchy. That means you need to store state somewhere other than the components and you need to dispatch events that are not attached to the component hierarchy. Also, a one way data flow has well known benefits as described by things like CQRS, RabbitMQ, and MediatR.
What are some alternatives?
language-ext - C# functional language extensions - a base class library for functional programming
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Polly - Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.
Brighter - A framework for building messaging apps with .NET and C#.
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
AutoMapper - A convention-based object-object mapper in .NET.
Jering.Javascript.NodeJS - Invoke Javascript in NodeJS, from C#
Streams - A lightweight F#/C# library for efficient functional-style pipelines on streams of data.
Coravel - Near-zero config .NET library that makes advanced application features like Task Scheduling, Caching, Queuing, Event Broadcasting, and more a breeze!
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]