InfluxDB vs. Memfault

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

If you're running a fleet of embedded devices that has a tight RAM, CPU, & power footprint, Memfault is a must-have. From managing firmware deployments to monitoring every facet of the device lifecycle and performance, this is a solution that is built with a founding team that are the absolute best in the industry. They know your chipset and OS extraordinarily well and in some cases have been able to work directly with the chip vendors to provide support for their SDKs. With Memfault's help, our chip vendor diagnosed an issue in their BLE SDK and dramatically decreased the number of crash events on our devices.

Incentivized

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

Incentivized

• GUI based administrator console

Incentivized

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized