homemade-di VS EstEID.Blazor

I hope the concept of dependency injection is clear to you now. Feel free to look up the final code on GitHub as I worked a little bit on it for improvements and also tested it for the various use-cases.

If I understand correctly you can have make a class that gets initialized on startup. For singleton the constructor can have a task that wont resolve which isnt ideal but will work. How many queries you make to the database then is your own to implement. For example lets say we use entitiyframework. You can make a permarunning task in a singleton class constructor that will just keep some data in memory. Then that Task calls the savechanges() every one hour. If there is a power outage obviously you will have hour lost of data but thats not the question. That class will get initialized on program startup and will keep running until you shut it down. I did long ago a tool to read data from Smart Cardsthat utilized a singleton class to fire events and then blazor to use as UI. The idea is that since there is ever only 1 instance of that class the events fired will propagate to every subscriber. This way you can have a client to display data, a client to say log info etc. Similar approach can be used to handle data in your case. You can attach several "screens" through browser to make same data be displayed in several locations etc. The public bit i can share as an example is here: https://github.com/elraito/EstEID.Blazor. It is trivial to track when something gets initilized or fires since we do have console.writeline() :)