frostdb
marketstore
| frostdb | marketstore | |
|---|---|---|
| 5 | 31 | |
| 1,210 | 1,819 | |
| 1.1% | 0.2% | |
| 9.5 | 0.0 | |
| 3 days ago | 10 months ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
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
marketstore
-
anyone have experience writing data to parquet files? Is there a better alternative for storing large amounts of financial tick data?
I'm also open to the idea of a better tick-storage solution, but after trying many out like Alpaca Marketstore, TimescaleDB, etc. it seems like parquet files would fit my needs better and give me more flexibility for replaying data into my algorithms.
- marketstore: NEW Data - star count:1654.0
- marketstore: NEW Data - star count:1583.0
What are some alternatives?
column - High-performance, columnar, in-memory store with bitmap indexing in Go
alpaca-trade-api-python - Python client for Alpaca's trade API
parquet-go - Go library to read/write Parquet files
kaspad - Kaspad is the reference full node Kaspa implementation written in Go (golang).
clover - A lightweight document-oriented NoSQL database written in pure Golang.
tstorage - An embedded time-series database
levigo - levigo is a Go wrapper for LevelDB
cnosdb - A cloud-native open source distributed time series database with high performance, high compression ratio and high availability. http://www.cnosdb.cloud
parquet-go - pure golang library for reading/writing parquet file
alpaca-trade-api-js - Node.js library for Alpaca Trade API.
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
bbgo - The modern cryptocurrency trading bot framework written in Go.