anna VS foundationdb

Compare anna vs foundationdb and see what are their differences.

anna

A low-latency, cloud-native KVS (by hydro-project)

foundationdb

FoundationDB - the open source, distributed, transactional key-value store (by apple)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
anna foundationdb
3 21
678 13,898
0.0% 2.0%
0.0 9.8
almost 3 years ago 1 day ago
C++ C++
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

anna

Posts with mentions or reviews of anna. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-16.

foundationdb

Posts with mentions or reviews of foundationdb. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-14.
  • Figma's Databases team lived to tell the scale
    5 projects | news.ycombinator.com | 14 Mar 2024
    Actually, Apple does this for iCloud! They use FoundationDB[1] to store billions of databases, one for each user (plus shared or global databases).

    See: https://read.engineerscodex.com/p/how-apple-built-icloud-to-...

    Discussed on HN at the time: https://news.ycombinator.com/item?id=39028672

    [1]: https://github.com/apple/foundationdb https://en.wikipedia.org/wiki/FoundationDB

  • WASM by Example
    16 projects | news.ycombinator.com | 15 Nov 2023
    > I wondered if perhaps this WASM use case for a cross-language library was already just as possible and ergonomic using language bindings and maybe thats why this use case doesnt seem like a big deal to people.

    Yeah that’s the reason. You don’t notice it a lot of the time, but FFIs are everywhere already. The most common foreign function interface is basically the ability to call C code, or have functions made available to C code. C is used because everyone knows it and it’s simple. And most languages either compile to native code (eg rust) - which makes linking to C code easy. Or the runtime is implemented in C or C++ (eg V8, Ruby). In languages like that, the standard library is already basically implemented via a FFI to C/C++ code.

    I’ve got an iOS app I’m working on that’s half rust and half swift, with a touch of C in the middle. The bindings work great - the whole thing links together into one binary, even with link time optimizations. But the glue code is gross, and when I want to fiddle with the rust to Swift API I need to change my code in about 4 different places.

    Most FFIs are a one to many relationship in that if you write a clean C API, you can probably write bindings in every language. But you don’t actually want to call naked C code from Ruby or Javascript. Good bindings will make you forget everything is done via ffi. Eg numpy. I haven’t looked at the wasm component model proposal - I assume it’s trying to make this process cleaner, which sounds lovely.

    I maintain the nodejs bindings for foundationdb. Foundationdb bindings are all done via ffi linking to their C code. And the API is complex, using promises and things. I find it really interesting browsing their official bindings to go, Java, Python and Ruby. Same bindings. Same wrapped api. Same team of authors. Just different languages. And that’s enough to make the wrapper wildly different in every language. From memory the Java ffi wrapper is 4x as much code as it is in Ruby.

    https://github.com/apple/foundationdb/tree/main/bindings

  • JDK 21 Release Notes
    6 projects | news.ycombinator.com | 19 Sep 2023
    Isn’t apple server on C/C++?

    They have their own db in that

    https://github.com/apple/foundationdb

  • How FoundationDB works and why it works
    5 projects | news.ycombinator.com | 18 Sep 2023
    > 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: A Distributed Key-Value Store
    13 projects | news.ycombinator.com | 3 Jul 2023
    13 projects | news.ycombinator.com | 3 Jul 2023
    I don't recall any of those details but the test involved injecting a bogus block device that always returns garbage, and noting that this results in garbage records returned from client queries. And I don't think those kinds of issues have been eradicated, browsing through their github issues there are people trying to recover corrupted clusters. https://github.com/apple/foundationdb/issues/2480
    13 projects | news.ycombinator.com | 3 Jul 2023
    Those tests are not the implementations of the tests, just specifying the test case. But I found the implementations. I am not sure if this is all of them, but it seems to cover the major tests.

    https://github.com/apple/foundationdb/tree/main/fdbserver/wo...

  • Install FoundationDB in Gentoo
    2 projects | /r/Gentoo | 3 Jul 2022
    For my current job, I have to install FoundationDB (they have a github repo) as a dependency for the project's code.
  • Anna: Key-Value Store for Any Scale
    2 projects | news.ycombinator.com | 29 Apr 2022
    To clarify, FoundationDB has some documented multi-region features, but it's not at all clear that anybody who runs it at scale relies on those multi-region features [1]. Even if they do, it's not obvious they run this Fearless DR mode at any appreciable latency.

    Geo-replication is an area where Anna really shines, and foundation pays severe costs. All of the concurrency control problems have contention footprints on the order of round-trips. Fully optimistic concurrency control needs to expose backoffs quite a few round-trips to be live. Even pessimistic concurrency control requires some number of round trips, probably at least 1.5 optimally, but in practice in most tuned systems, probably 3. A heck of a lot of use cases make sense at 0 global RTTs and don't at 1+. The ability to tell the database how to manage concurrency, and then providing causal is ultimately the best you can do. That's awesome.

    At the end of the day, I have to believe that there's a whole big mess of applications we'll build this, on systems in the portion of the design space Anna is choosing, one day. This is only recently not cutting edge research, but it's definitely still research. We don't know how to model these concepts at a high-level and in a composable way where the masses of software developers can engage with them.

    It's interesting to think about how long ago we were graced with BAYOU [2], that thing was ahead of its time. I suspect it's going to take a little while longer before these sorts of techniques make their way into data storage primitives we think of as part of the standard vernacular, but I believe we'll get there eventually.

    Databases are fun!

    [1] https://github.com/apple/foundationdb/wiki/Multi-Region-Repl...

  • FoundationDB: A Distributed Unbundled Transactional Key Value Store
    4 projects | news.ycombinator.com | 11 Mar 2022
    (Disclaimer: affiliated)

    Redwood isn't "completed", but it's not unavailable. Evaluating it via `fdbcli> configure ssd-redwood-1-experimental ` is encouraged, but it hasn't seen sufficiently deep evaluation and verification that it's been set as the default ssd storage engine yet.

    Not all releases got blog posts. Which ones did honestly had far more to do with the people involved in the releases at the time than any technical merits. This is the first feedback that I've seen where the blog posts were used as a signal of worthiness or stability, so we'll see if we can try to be a bit more responsible about making release posts.

    Releases that are posted to the downloads page are all equally considered "ready to go". They appear a bit slower than what gets tagged on github, as the production environments in the core set of companies supporting FDB development are used as the last stage of QA before an official release. (Though this distinction might be less clear as the downloads page was recently redirected to the github release artifacts page.)

    You can find the 7.0 release notes at https://github.com/apple/foundationdb/blob/main/documentatio..., which will appear in the documentation once the public site is updated to 7.0 (which happens once the first official, public release is blessed).

    All that said, the regular release cadence so far has been about every 6 months, which I think still does qualify as "glacial".

What are some alternatives?

When comparing anna and foundationdb you can also consider the following projects:

swift-evolution - This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.

FASTER - Fast persistent recoverable log and key-value store + cache, in C# and C++.

KeyDB - A Multithreaded Fork of Redis

SSDB - SSDB - A fast NoSQL database, an alternative to Redis

password-manager-resources - A place for creators and users of password managers to collaborate on resources to make password management better.

containers - Bitnami container images

xcodis - Yet another redis proxy based on codis(https://github.com/wandoulabs/codis)

codis - Proxy based Redis cluster solution supporting pipeline and scaling dynamically

fdb-document-layer - A document data model on FoundationDB, implementing MongoDB® wire protocol

fdb-kubernetes-operator - A kubernetes operator for FoundationDB

docker - Docker - the open-source application container engine

dynomite - A generic dynamo implementation for different k-v storage engines