Ok, I wrote almost everything in the title, but let me expand on that a bit :)

As you might guess, the “alien engine” is Fusion — I still struggle to find a perfect one-line description for it :)

Thanks to Dmitry Filippov (̶g̶i̶r̶l̶s̶, just look at this huge pull request!), Fusion got .NET Standard 2.0 / .NET Framework 4.7+ support. Crazy, but almost every test runs…

An interesting observation I’ve made recently is that nearly all UI architectures are quite similar.

Let’s start from Flux:

Flux UI architecture

A brief description of what happens here:

If you believe Virtual DOM is a “lightweight copy” of a real DOM helping to speed up the updates by batching them together— continue reading. Albeit being correct, it’s a highly misleading answer. …

This is Fusion too. But not a real one.

This is a short overview of features added to Fusion over the last 3 months. Some of them are already covered in the Tutorial; I’ll definitely describe the rest soon.

The same day .NET 5 was released I shared a single screenshot showing how much faster .NET 5 is relatively to .NET Core 3.1. I promised to share more data later — and here it is.

1. Fusion’s Caching Test — running on Ubuntu + Intel and AMD CPUs

Code: https://github.com/servicetitan/Stl.Fusion.Samples , see “Caching Sample” section there.

Overall, these tests stress an API…

I migrated Fusion to .NET 5 today — and honestly, I was absolutely astonished by the performance boost it brings:

The output is produced by Fusion’s “Caching” sample, which uses EF Core 5 and ASP.NET Core. The speed on tests producing 20M+ operations/s (#1, #3) is mainly constrained by Fusion’s…

Fusion — a small library created as an attempt to challenge the existing architecture of high-load and real-time apps — is going to be 4 months old soon. Here is what happened over these months:

Even though Amazon’s example isn’t unique in the context of this post, I’ll use it as a first example of efficiency of a modern web service:

Disclaimer: I am the author of Stl.Fusion — an open-source library helping to address the long-standing problem described in this post. But the problem is real, and the post is relevant even if this library won’t exist.

What’s the biggest difference between the modern and the future web apps?

To answer this question, let’s ask the opposite one first: what’s the most…

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store