Blazor Server and Blazor WebAssembly (client) don't store state by default, resulting in a subpar user experience. Learn what makes up state in Blazor apps and discover solutions implemented in shared, easy to use libraries that take advantage of browser cache and server persistence to solve Blazor state management.
WebAssembly now lives outside of the browser thanks to the WebAssembly System Interface (WASI) and runtimes like Wasmer and Wasmtime. Learn how to build and run your own WASI modules without leaving your favorite browser.
Durable functions enable implicit and explicit state management for serverless workflows and accommodate a variety of patterns. A new addition, the HTTP task, helps manage interactions with HTTP endpoints including error handling and support for long polling.