frostdb
moss
frostdb | moss | |
---|---|---|
5 | 2 | |
1,210 | 941 | |
1.1% | 0.0% | |
9.5 | 0.0 | |
3 days ago | about 2 years ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
frostdb
-
Polar Signals Cloud Is Generally Available
> In addition to that we built a custom columnar database
I did some digging in your blog history and it seems that is referencing https://www.polarsignals.com/blog/posts/2022/07/22/frostdb-i... and digging into the "but why?" section <https://github.com/polarsignals/frostdb#why-you-should-use-f...> seems to imply you favored the embedded feature over having something standalone, but I would enjoy hearing (or reading a blog post!) about why you felt it was a better use of your engineering to make your own columar DB versus using one of the existing columanr dbs that I have seen referenced a ton in other Show HN announcements around both logging and metrics services
-
anyone have experience writing data to parquet files? Is there a better alternative for storing large amounts of financial tick data?
We use clickhouse, but i would take a look at https://github.com/polarsignals/frostdb
- Open Source Databases in Go
-
ArcticDB: A Database for Observability
Hey all, one of the creators of ArcticDB here. We're going to be around for a while and answer any questions you might have about it!
It's open source so if you just want to check out the repo: https://github.com/polarsignals/arcticdb
-
arcticDB: embedded columnar database written in Go
Direct link to the DB project -> https://github.com/polarsignals/arcticdb
moss
-
Open Source Databases in Go
moss - Moss is a simple LSM key-value storage engine written in 100% Go.
-
But how, exactly, databases use mmap?
I decided to dig through a database source code to answer that question. There are plenty of databases that use mmap. Some of them decided to not use anymore. Some examples: SQLite has an option of accessing disk content directly using memory-mapped I/O[1], it seems LevelDB used to use but it changed it[2], Lucene has an option with MMapDirectory[3], LMDB uses mmap[4], a simple key/value in-memory database from Counchbase called moss uses mmap for durability of in-memory data[5] and MongoDB removed mmap storage engine for WiredTiger[6].
What are some alternatives?
column - High-performance, columnar, in-memory store with bitmap indexing in Go
badger - Fast key-value DB in Go.
parquet-go - Go library to read/write Parquet files
bolt
clover - A lightweight document-oriented NoSQL database written in pure Golang.
tidb - TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at : https://tidbcloud.com/free-trial
marketstore - DataFrame Server for Financial Timeseries Data
prometheus - The Prometheus monitoring system and time series database.
levigo - levigo is a Go wrapper for LevelDB
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
parquet-go - pure golang library for reading/writing parquet file
fastcache - Fast thread-safe inmemory cache for big number of entries in Go. Minimizes GC overhead