-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Before checking this out, people might want to take a look through the issues and pull requests of which there are 500+ and 50+ respectively [1]. I was really optimistic about this project and it was headed in a great direction, but it's not in a production ready state, and it seems that the main guy behind it has decided to move onto other things. It's been about a year since there was any significant activity.
I just mention this because a lot of these little issues might only become more apparent after integrating the db into your project and so it can be a bit annoying. I ended up swapping to Linq2DB [1]. It's something, more or less, similar offering an ORM/LINQ type system as well as the ability to also use direct SQL if desired. But the neat thing is that it also uses a standardized API for the LINQ query language, so you can do things like swap from SQLite to PostgreSQL in one* line of code, so long as you're not using any provider specific extensions.
[1] - https://github.com/mbdavid/LiteDB
[2] - https://github.com/linq2db/linq2db
One reason:
SQLite is slower than LiteDB in this benchmark project created by the LiteDB inventor
https://github.com/mbdavid/LiteDB-Benchmark
https://github.com/mbdavid/LiteDB/issues/291
Another (lesser) reason is the similarity to MongoDB methods, if that's what you are used to it will feel familiar, but no MongoDB server needed.
Spot on, this was the original intent of the linked implementation but the PR eventually did not progress and got rejected[0].
However, it might not be off the table yet, because scaling per core is dramatically better especially in moderate to write-heavy scenarios which remains the main use case for ConcurrentDictionary. I have been benchmarking it on arm64 lately and it shows different numbers much more favoring non-blocking implementation without any regressions discussed in the PR.
[0] https://github.com/dotnet/runtime/pull/50337
Before checking this out, people might want to take a look through the issues and pull requests of which there are 500+ and 50+ respectively [1]. I was really optimistic about this project and it was headed in a great direction, but it's not in a production ready state, and it seems that the main guy behind it has decided to move onto other things. It's been about a year since there was any significant activity.
I just mention this because a lot of these little issues might only become more apparent after integrating the db into your project and so it can be a bit annoying. I ended up swapping to Linq2DB [1]. It's something, more or less, similar offering an ORM/LINQ type system as well as the ability to also use direct SQL if desired. But the neat thing is that it also uses a standardized API for the LINQ query language, so you can do things like swap from SQLite to PostgreSQL in one* line of code, so long as you're not using any provider specific extensions.
[1] - https://github.com/mbdavid/LiteDB
[2] - https://github.com/linq2db/linq2db
A few years ago, I needed faster SQLite interop than Microsoft.Data.Sqlite, and ended up writing my own: https://github.com/zmj/sqlite-fast
The ergonomics could be better, but this enabled query execution to avoid heap allocations and reflection.
Related posts
-
System.Text.Json will not directly support System.Runtime.Serialization attributes, telling developers "Just do it yourself"
-
DateOnly And TimeOnly Types In .NET 6
-
.NET 6 - Preview 2 (Apple Silicon)
-
Airline keeps mistaking 101-year-old woman for baby
-
The software industry rapidly convergng on 3 languages: Go, Rust, and JavaScript