I'm learning ASP.NET Core 2, with Entity Framework Core. A real use-case scenario is a small management of a production process. I have some persistent table like customers, orders, machines, etc... but I also have some "live" tables.
Example: the current status of the machines. This information is valid only at the present moment. Every, say 1 second, I will get new updated information about the machine's status.
To show these values on a web page (Razor) is very useful to define a Model. But due to the very high refresh rate, I'm not sure storing them in a regular database is the best idea. Furthermore on startup I must delete all data because I need to receive the actual one.
Hence, I think a "in-memory" database could be a solution, but the official documentation seems to discourage this practice:
The InMemory provider is useful when you want to test components using something that approximates connecting to the real database, without the overhead of actual database operations.
Am I interpreting correctly the above sentence? Or they just propose ONE of the possible use of such a database?