swift-corelibs-libdispatch
tigerbeetle
swift-corelibs-libdispatch | tigerbeetle | |
---|---|---|
3 | 45 | |
2,426 | 7,207 | |
0.8% | 7.7% | |
6.5 | 9.9 | |
7 days ago | 7 days ago | |
C | Zig | |
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.
swift-corelibs-libdispatch
-
Is Parallel Programming Hard, and, If So, What Can You Do About It? v2023.06.11a
GCD/libdispatch is a fantastic approach to concurrency and you can build and install support for non-Apple operating systems:
https://github.com/apple/swift-corelibs-libdispatch
Here’s a simple echo server:
https://github.com/williamcotton/c_playground/blob/master/sr...
Here’s a simple multithreaded database pool:
https://github.com/williamcotton/express-c/blob/master/src/d...
-
Cross-platform I/O built on io_uring and kqueue (in TigerBeetle)
One of the reasons is that libdispatch's I/O functions introduce extra dynamic allocations for internal queueing via `dispatch_async` ([0],[1],[2]) and from an API perspective of realloc-ing ([3]) an internally owned ([4]) buffer.
TigerBeetle, on the other hand, statically allocates all I/O buffers upfront ([5]), treats these buffers as intrusively-provided typed data ([6]) (no growing/owned buffers), and does internal queueing without synchronization or dynamic allocation ([7]).
[0]: https://github.com/apple/swift-corelibs-libdispatch/blob/469...
-
What are the best books/courses for rigorous study of concurrency in iOS?
If you want iOS in particular, read the source of GCD itself.
tigerbeetle
-
Redis Re-Implemented with SQLite
I'm waiting for someone to implement the Redis API by swapping out the state machine in TigerBeetle (which was built modularly such that the state machine can be swapped out).
https://tigerbeetle.com/
-
The Fastest and Safest Database [video]
I fully agree with what Prime says at the end - Joran has really set a new bar here for all future database presentations.
Hearing that the entire TigerBeetle domain logic lives in a single file [0] (and is intended to be pluggable for other OLTP use cases!) makes it 1000% more tempting to spend the weekend getting up to speed with Zig.
[0] https://github.com/tigerbeetle/tigerbeetle/blob/main/src/sta...
-
Building a Scalable Accounting Ledger
Why would you want to build your own accounting ledger from scratch? Accounting is a completely new domain for most engineers, and TigerBeetle (https://tigerbeetle.com/) already solves this problem.
- Tiger Style
- Tigerbeetle's Storage Fault Model
- Factor is faster than Zig
-
The Raft Consensus Algorithm
Maelstrom [1], a workbench for learning distributed systems from the creator of Jepsen, includes a simple (model-checked) implementation of Raft and an excellent tutorial on implementing it.
Raft is a simple algorithm, but as others have noted, the original paper includes many correctness details often brushed over in toy implementations. Furthermore, the fallibility of real-world hardware (handling memory/disk corruption and grey failures), the requirements of real-world systems with tight latency SLAs, and a need for things like flexible quorum/dynamic cluster membership make implementing it for production a long and daunting task. The commit history of etcd and hashicorp/raft, likely the two most battle-tested open source implementations of raft that still surface correctness bugs on the regular tell you all you need to know.
The tigerbeetle team talks in detail about the real-world aspects of distributed systems on imperfect hardware/non-abstracted system models, and why they chose viewstamp replication, which predates Paxos but looks more like Raft.
[1]: https://github.com/jepsen-io/maelstrom/
[2]: https://github.com/tigerbeetle/tigerbeetle/blob/main/docs/DE...
- Fastest Branchless Binary Search
-
CWE Top Most Dangerous Software Weaknesses
> There is no reason to use a memory unsafe language anymore, except legacy codebases, and that is also slowly but surely diminishing. I'm still yet to hear this amazingly compelling reason that you just need memory unsafe languages. In terms of cost/benefits analysis, memory unsafety is literally all costs.
Tell that to the authors of new memory unsafe languages (like Zig) and creators of new project in those languages (like https://tigerbeetle.com) :(
- Problems of C, and how Zig addresses them
What are some alternatives?
Hopac - http://hopac.github.io/Hopac/Hopac.html
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
c_playground - C Playground
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
express-c - Fast, unopinionated, minimalist web framework for C
bun - Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
ThreadPool - A simple C++11 Thread Pool implementation
reshade - A generic post-processing injector for games and video software.
rafiki - An open-source, comprehensive Interledger service for wallet providers, enabling them to provide Interledger functionality to their users.
Box2D - Box2D is a 2D physics engine for games
raft - Golang implementation of the Raft consensus protocol
PyOxidizer - A modern Python application packaging and distribution tool