foundationdb
swift
foundationdb | swift | |
---|---|---|
21 | 215 | |
13,991 | 66,003 | |
0.7% | 0.4% | |
9.8 | 10.0 | |
4 days ago | about 3 hours ago | |
C++ | C++ | |
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.
foundationdb
-
Figma's Databases team lived to tell the scale
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
-
Maybe Getting Rid of Your QA Team Was Bad
Is this the language in question? https://github.com/apple/foundationdb/blob/main/flow/README....
-
WASM by Example
> 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
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
> 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
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
- Apple/FoundationDB: FoundationDB
- FoundationDB Design Internals
-
Install FoundationDB in Gentoo
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
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...
swift
-
Evolving the Go Standard Library with math/rand/v2
This algorithm produces biased result with probability 1/2^(32-bitwidth(N)). Using 64 or 128 random bits can make the bias practically undetectable. Comprehensive overview of the approach can be found here: https://github.com/apple/swift/pull/39143
- Swift: Differentiable Programming Manifesto
-
Embedded Swift on the Raspberry Pi Pico
Because of C/C++ interop, and integration with CMake, you can just add Swift to a Zephyr project and it pretty much Just Works. [The docs](https://github.com/apple/swift/blob/main/docs/EmbeddedSwift/...) should mostly apply to the Zephyr SDK as well.
-
A Deep Dive Into Observation: A New Way to Boost SwiftUI Performance
Fortunately, the Observation framework is part of the Swift 5.9 standard library. We can learn more information by examining its source code.
-
Swift was always going to be part of the OS
They do! See https://github.com/apple/swift/blob/main/docs/LibraryEvoluti...
You can also see an example of what a different high level language integration with Swift ABI looks like here: https://github.com/dotnet/designs/blob/main/proposed/swift-i...
-
Differentiable Swift
So is differentiable Swift a package for Swift or is it part of the Swift standard library? The video says go to swift.org but I can't find any info about differentiable Swift on that site.
-
Beyond Backpropagation - Higher Order, Forward and Reverse-mode Automatic Differentiation for Tensorken
Swift's Differentiable Programming Manifesto. Swift has a powerful differentiable programming component, integrated with the compiler.
-
Kotlin Multiplatform for Android and iOS Apps
You can do the same thing the other way around - https://github.com/apple/swift/blob/main/docs/Android.md.
-
This isn’t the way to speed up Rust compile times
Codable (along with other derived conformances like Equatable, Hashable, and RawRepresentable) is indeed built in to the compiler[0], but unlike Serde, it operates during type-checking on a fully-constructed AST (with access to type information), manipulating the AST to insert code. Because it operates at a later stage of compilation and at a much higher level (with access to type information), the work necessary is significantly less.
With ongoing work for Swift macros, it may eventually be possible to rip this code out of the compiler and rewrite it as a macro, though it would need to be a semantic macro[1] rather a syntactic one, which isn't currently possible in Swift[2].
[0] https://github.com/apple/swift/blob/main/lib/Sema/DerivedCon...
-
How does Swift implement primitive types in its standard library?
`Int` is a regular struct with a single stored property of type `Builtin.Word` . But the latter is a magical compiler built-in. Source for integer types is generated from this template - https://github.com/apple/swift/blob/9da65ca0a15fdf341649c994b0a77ec3b71f2687/stdlib/public/core/IntegerTypes.swift.gyb
What are some alternatives?
swift-evolution - This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.
solidity - Solidity, the Smart Contract Programming Language
FASTER - Fast persistent recoverable log and key-value store + cache, in C# and C++.
cpp-lazy - C++11/14/17/20 library for lazy evaluation
password-manager-resources - A place for creators and users of password managers to collaborate on resources to make password management better.
Elixir - Elixir is a dynamic, functional language for building scalable and maintainable applications
fdb-document-layer - A document data model on FoundationDB, implementing MongoDB® wire protocol
tree-sitter - An incremental parsing system for programming tools
fdb-kubernetes-operator - A kubernetes operator for FoundationDB
hummingbird - Hummingbird compiles trained ML models into tensor computation for faster inference.
docker - Docker - the open-source application container engine
lobster - The Lobster Programming Language