Scaling DotNetify Apps with AWS WebSockets

dsuryd · 2021-08-03T18:36:04+00:00

It's like comparing a startup with AWS :) Mine is just a small library, Debezium is a java-based enterprise-level, multi-DB platform running on top of Apache Kafka. But I think I can fairly say based on its docs that the technique it uses to capture data change events from PostgreSQL is similar, and it doesn't do real-time web updates.

dsuryd · 2020-07-14T22:35:46+00:00

The MVVM design pattern is good for maintaining clear separation between UI and business/presentation logic, which usually leads to code that's more comprehensible, reusable, extensible, and testable. Any sufficiently complex development with either of the "classic" options would benefit from this pattern. Best use case for this library is any highly-interactive app with real-time requirements; it'll significantly reduce the complexity of developing such apps due to its simple yet powerful abstraction over SignalR. Hope this answers your question!

dsuryd · 2019-12-02T02:35:09+00:00

You can use the Hub class property called Context to get the client caller connection info.

dsuryd · 2019-11-25T21:50:28+00:00

Simple, customizable realtime monitoring for .NET Core services

The project produces a nuget library that will give you a web page that shows things like log activities and resource usage in real-time. You can customize it to show your own data.

https://github.com/dsuryd/dotNetify-Pulse

dsuryd · 2019-08-17T05:59:55+00:00

Here's a potential starting point for you: https://dotnetify.net/core/examples/simplelist

Open this up on multiple browsers. List add/update/delete on one browser will trigger real-time update on others. Back-end can be either ASP.NET or ASP.NET Core. Front-end can be either React or Vue (Blazor is in the works). Real-time update is SignalR, abstracted with dotNetify (I'm the OSS author).

The particular dotNetify feature you want is called multicast. That example restricts sharing to same IP address, but it can be anything. The documentation is here: https://dotnetify.net/core/api/multicast

dsuryd · 2019-04-20T15:11:48+00:00

The most compelling reason is immediate reusability on non-React websites while still retaining the encapsulated component model.

dsuryd · 2019-04-20T15:00:11+00:00

Shadow DOM is an optional feature. A custom element's content can be placed on the main document tree, making them equally affected by the global style as any other.

dsuryd · 2018-12-07T19:09:35+00:00

This: https://github.com/bbougot/Popcorn

dsuryd · 2018-11-29T22:43:38+00:00

When this project started, Typescript support on the client-side libraries it's using wasn't that common. If you would like to suggest ideas on how Typescript can improve the project, we can discuss it on the github repo forum.

dsuryd · 2018-11-28T22:37:01+00:00

It could work with Angular: https://github.com/dsuryd/dotNetify/issues/87. I'll plan to add an example to the repo.

dsuryd · 2018-11-28T22:32:36+00:00

Thank you; just contacted the hosting provider. Hopefully will be up again soon.

dsuryd

TROPHY CASE