3. Best practices for storing data / database
MagicMirror² v2.5.0 is available! For more information about this release, check out this topic.

Best practices for storing data / database

  • S

    Hi,
    I’m working on a module that will need to store data into a database.

    Is there a best practice on Magic Mirrror for that? Or I jut need to install a lib which could do the job like nedb?

    I’m looking for a lightweight timeseries database to store a float every X seconds.

    0
  • C

    I would think from a high level architecture view you would be better served running your database on a different node and doing a read every X seconds for display on the mirror. You could run the system stats module to monitor cpu and volatile memory management while testing various approaches, but if you accrue historical data very quickly you could exceed the storage limit on the operating partition and cause performance issues.
    My understanding of hardware/software architecture is a bit dated, however, so someone with more experience on node.js, electron and the various bits that support the Magic Mirror application may have a better response.

    0