fdb-kubernetes-operator
fdb-record-layer
fdb-kubernetes-operator | fdb-record-layer | |
---|---|---|
3 | 4 | |
226 | 564 | |
1.8% | 0.4% | |
9.3 | 9.8 | |
2 days ago | 7 days ago | |
Go | Java | |
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.
fdb-kubernetes-operator
-
How FoundationDB works and why it works
> Any meaningful technology is open source.
Clearly untrue, however FoundationDB is open source, with a permissive license.
https://github.com/apple/foundationdb
So is much of the operational tooling for it:
https://github.com/FoundationDB/fdb-kubernetes-operator
- FoundationDB Kubernetes Operator gets its v1.0.0 release
-
FoundationDB: A Distributed Unbundled Transactional Key Value Store
I understand nothing of helm, but https://github.com/FoundationDB/fdb-kubernetes-operator/pull... seems to suggest yes?
fdb-record-layer
-
Figma's Databases team lived to tell the scale
FoundationDB is really just a set of structures and tools to build any type of database you want on top of a solid foundation.
"FoundationDB decouples its data storage technology from its data model. FoundationDB’s core ordered key-value storage technology can be efficiently adapted and remapped to a broad array of rich data models. Using indexing as an example, FoundationDB’s core provides no indexing and never will. Instead, a layer provides indexing by storing two kinds of key-values, one for the data and one for the index."
https://apple.github.io/foundationdb/layer-concept.html
Then existing standard layers like the Record layer, providing "(very) roughly equivalent to a simple relational database" providing structured types, index, complex types, queries, etc.
https://github.com/FoundationDB/fdb-record-layer
-
FoundationDB: A Distributed Key-Value Store
> That being said, I wish there were more layers as the functionality out of the box is very very limited.
The record layer https://github.com/FoundationDB/fdb-record-layer which allows to store protobuf, and define the primary keys directly in those is truly amazing:
https://github.com/FoundationDB/fdb-record-layer/blob/main/d...
- FoundationDB: A Distributed Unbundled Transactional Key Value Store
-
Show HN: A strongly-typed document DB that runs on any transactional KV store
This looks really promising! Could you provide at a high-level what this aims to offer over FoundationDB's RecordLayer[1]?
[1] https://github.com/FoundationDB/fdb-record-layer
What are some alternatives?
foundationdb - FoundationDB - the open source, distributed, transactional key-value store
Permazen - Language-Natural Persistence Layer for Java
tigris - Tigris is an Open Source Serverless NoSQL Database and Search Platform.
hyhac - A HyperDex Haskell Client
deepr - A lightweight alternative to GraphQL
RefineDB - A strongly-typed document database that runs on any transactional key-value store.
TablaM - The practical relational programing language for data-oriented applications
refound - a RethinkDB implementation backed by FoundationDB
relic - Functional relational programming for Clojure(Script).