LocalStorage VS Hangfire

if its like less than 30 items u can just use https://github.com/Blazored/LocalStorage

You store the token in local storage. This is a library that will give you access to that. Blazored

Blazored LocalStorage - for Tokens and Authentication Stuff

The library make use of Blazored LocalStorage for storing cache data.

I use a library called Blazored LocalStorage for the WASM project to store client side data like preferences and auth stuff. This, it seems, is not supported in MAUI. Although MAUI starts a web server, it does not store data in the 'browser'. Instead it uses an API called "Preferences" (Which is a pretty sweet interface, props MS) but now I find myself struggling how I can use one, or the other depending on the project.

I've built a few Blazor WASM apps and use Blazored LocalStorage to access it.

For Blazor, you need to either use a third-party library to set up INPC, or do this yourself. I do the latter. For example, I have a settings class. I use https://github.com/blazored/LocalStorage to store the settings in the browser, and set them up as a singleton.

If you only need key/value, I've been using this one. https://github.com/Blazored/LocalStorage

Unpopular opinion incoming... What I see is yet another way that the backend JS world is finally achieving something .NET had years ago[0].

Node/Deno/Bun/etc. + npm sounds super straightforward at first glance (and it is at first). But I've thought for years that it's far easier to be productive as an organization on .NET in Visual Studio, since it's simpler to design, deliver, and maintain infrastructure.

[0] https://www.hangfire.io/

you can read about it here HangFire Documentation

I mostly work in .NET, and typically use Hangfire, but all languages has similar frameworks

Its hard to tell what tool would be a best fit without more information, but I would suggest looking at Hangfire for background job processing: https://www.hangfire.io/

You might want to look at https://www.hangfire.io/. Their docs explain how to set up queues: https://docs.hangfire.io/en/latest/background-processing/configuring-queues.html

In this article we looked at how to use Hangfire to schedule background jobs in ASP.NET according to our requirements. In a follow up article, I will talk about using Hangfire with a Redis storage. To learn more about Hangfire, you can visit the official website.

Easy to understand if you want to implement your own background service. If you want a more easy and complete tool you can use hangfire.

Try https://www.hangfire.io/

If, as you stated, you really need to use your own servers, that seems exactly like a job for Hangfire.