Hot Chocolate VS Rx.NET

have a look here https://youtu.be/qrh97hToWpM https://chillicream.com/

There are some libraries which allows you to declare some class with more or less arbitrary methods which will be called by it at runtime. I believe many of them do that in optimal way, not just using usual reflection. One of the examples is HotChocolate library https://github.com/ChilliCream/hotchocolate . You declare class with arbitrary methods which contain arbitrary arguments. "Arbitrary" doesn mean arbitrary at all, but if parameter type is registered in DI or marked by specific attribute, it can be passed to the method.

At work we are considering using GraphQL to build our read-only data-APIs using .NET 6, EF Core and SQL Server. Looking at the ecosystem the most relevant plattforms seems to be graphql-dotnet and ChilliCream.

I'm starting a brand new project. Looks like if we want to do GraphQL in .NET, it's either graphql-dotnet or Hot Chocolate. Both look pretty good on paper.

If you know it better: Please try statically typed generated graphql queries in C# (like write the graphql queries, have a graphql schema, then get generated C# types which resemble the query, the only thing I've found that could do it was https://chillicream.com/docs/strawberryshake and there I quickly hit this bug with super simple queries containing unions: https://github.com/ChilliCream/hotchocolate/issues/4662

If you don't know Hot Chocolate framework, feel free to read about it on chillicream.com (official website) and feel free to join the great community (which is always willing to help) on slack

I love using Hot Chocolate in C# ❤

Hotchocolate GraphQL server. This is the most advanced server for a .Net environment. This article does not go into the basics and assumes some framework knowledge.

I think for the time being that's the case, yeah. I'm confirming with the great people over at https://github.com/ChilliCream/hotchocolate to see if we can somehow work around that.

DynamicData is a .NET library that brings the power of reactive programming to collections. It is built upon the principles of Reactive Extensions (Rx), extending these concepts to handle collections like lists and observables more efficiently and flexibly. DynamicData provides a set of tools and extensions that enable developers to manage collections reactively, meaning any changes in the data are automatically and efficiently propagated through the application.

One of the greatest things i discovered recently, is Reactive programming / Reactive Extensions ( https://github.com/dotnet/reactive ).

https://github.com/dotnet/reactive has a lot of different time related extensions for "events". Maybe you'll find something for yourself, if you google for rate limiting with reactive.

Install Reactive Extensions: https://github.com/dotnet/reactive

Another option is to use the RxJava library in Java. This library uses reactive programming principles to make it easy to write asynchronous and event-driven code. It's particularly well-suited for handling streams of data and allows you to write code that is both efficient and easy to read.

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.

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.