NeDB might be a bit more popular than TimescaleDB. We know about 7 links to it since March 2021 and only 5 links to TimescaleDB. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Yes! I plan to maintain it long-term! I will be rolling out some feature improvements and updates these few weeks. I still think Kong did a good job in crafting the product. I started using Insomnia in my previous company 3 years ago and our team loved it. What happened recently felt a little bit like the Unity fiasco (of course, in a much smaller scale). Though as a user I would say Kong had taken a bad turn, I'm... - Source: Hacker News / 8 months ago
At least for my needs, NeDB[0] is the best of both worlds for prototyping and early-stage production releases. It's human-readable, on-disk, greppable, still supports indexing and a subset of Mongo features while remaining serverless and in-memory. [0] https://github.com/louischatriot/nedb. - Source: Hacker News / almost 2 years ago
Local: Local specific logic. For example, code to write to a Nedb table. - Source: dev.to / about 2 years ago
What I'd do to get the best understanding of how NeDB works is to dive into the docs here. The primary things to keep in mind are that there can be other non-JSON data in those files, and that all of the document data is appended and periodically compacted, which means you'll often have an arbitrary number of duplicates and versions within the same file. Source: about 2 years ago
I've used https://github.com/louischatriot/nedb before but it may not meet your needs. Source: almost 3 years ago
(:alert: I work for Timescale :alert:) It's funny, we hear this more and more "we did some research and landed on Influx and ... Help it's confusing". We actually wrote an article about what we think, you can find it here: https://www.timescale.com/blog/what-influxdb-got-wrong/ As the QuestDB folks mentioned if you want a drop in replacement for Influx then they would be an option, it kinda sounds that's not what... - Source: Hacker News / 7 months ago
If you like PostgreSQL, I'd recommend starting with that. Additionally, you can try TimescaleDB (it's a PostgreSQL extension for time-series data with full SQL support) it has many features that are useful even on a small-scale, things like:. Source: over 1 year ago
I have built a Django server which serves up the JSON configuration, and I'd also like the server to store and render sensor graphs & event data for my Thing. In future, I'd probably use something like timescale.com as it is a database suited for this application. However right now I only have a handful of devices, and don't want to spend a lot of time configuring my back end when the Thing is my focus. So I'm... Source: over 2 years ago
I've seen a lot of benchmark results on timescale on the web but they all come from timescale.com so I just want to ask if those are accurate. Source: over 2 years ago
Ryan from Timescale here. We (TimescaleDB) just launched the second annual State of PostgreSQL survey, which asks developers across the globe about themselves, how they use PostgreSQL, their experiences with the community, and more. Source: about 3 years ago
PouchDB - Open-source JavaScript database inspired by Apache CouchDB that's designed to run well within the browser
InfluxData - Scalable datastore for metrics, events, and real-time analytics.
IndexedDB - IndexedDB is a low-level API for client-side storage of significant amounts of structured data, including files/blobs.
Prometheus - An open-source systems monitoring and alerting toolkit.
Redis - Redis is an open source in-memory data structure project implementing a distributed, in-memory key-value database with optional durability.
OpenTSDB - OpenTSDB is a distributed, scalable Time Series Database (TSDB) written on top of HBase.