FAQ

Real-Time State Synchronization

Fusion provides automatic real-time state synchronization across all clients, ensuring your application stays in sync without manual intervention. Changes are propagated instantly to all connected clients.

Distributed Caching and Dependency Tracking

Fusion's intelligent dependency tracking system automatically detects and manages data relationships, performing precise cache invalidation to optimize performance and reduce unnecessary computations.

Persistent Client-Side Caches

Built-in offline support with persistent client-side caching enables your application to work seamlessly even without an internet connection, with automatic synchronization when connectivity is restored.

Extremely Efficient RPC

Fusion's RPC system revolutionizes client-server communication by eliminating redundant network calls. It uses a sophisticated stale-while-revalidate strategy and speculative execution to batch hundreds of calls into single transmission frames, dramatically reducing network overhead.

UI State Management

Fusion seamlessly integrates UI state management into its core architecture, eliminating the need for separate state management libraries. This unified approach simplifies development and reduces complexity.

Unified Codebase for All Clients

Write once, run anywhere. Fusion enables you to maintain a single codebase that works across all Blazor platforms - Server, WebAssembly, and Hybrid/MAUI - while automatically optimizing for each platform's unique characteristics.

FAQ

What's the best place to ask questions related to Fusion?

Fusion @ Actual Chat is currently the best place to ask questions and track project updates.

Can I contribute to the project?

Absolutely. Just create your first pull request or report a bug. You can also contribute to Fusion Samples.

Can I use Fusion with server-side Blazor?

Yes, you can use it to implement the same real-time update logic there. The only difference here is that you don't need API controllers supporting Fusion publication in this case, i.e. your models might depend right on the server-side compute services (that's an abstraction you primarily deal with, that "hides" all the complexities of dealing with Computed<T> and does it transparently for you).

Can I use Fusion without Blazor at all?

The answer is yes – you can use Fusion in all kinds of .NET Core apps, though I guess the real question is ↓

Can I use Fusion with some native JavaScript client for it?

Right now there is no native JavaScript client for Fusion, so if you want to use Fusion subscriptions / auto-update features in JS, you still need a counterpart in Blazor that e.g. exports the "live state" maintained by Fusion to the JavaScript part of the app after every update.

There is a good chance we (or someone else) will develop a native JavaScript client for Fusion in the future.

Are there any benefits of using Fusion on server-side only?

Yes. Any service backed by Fusion, in fact, gets a cache, that invalidates right when it should. This makes % of inconsistent reads there is as small as possible.

Which is why Fusion is also a very good fit for caching scenarios requiring nearly real-time invalidation / minimum % of inconsistent reads.

API related questions (TBD)

TBD