FASTER
vitess
Our great sponsors
| FASTER | vitess | |
|---|---|---|
| 8 | 60 | |
| 6,199 | 17,834 | |
| 3.7% | 1.6% | |
| 7.2 | 9.9 | |
| 13 days ago | 6 days ago | |
| C# | Go | |
| MIT License | 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.
FASTER
-
A MySQL compatible database engine written in pure Go
You would be surprised by performance of modern .NET :)
Writing no-alloc is oftentimes done by reducing complexity and not doing "stupid" tricks that actually work against JIT and CoreLib features.
For databases specifically, .NET is actually positioned very well with its low-level features (intrisics incl. SIMD, FFI, struct generics though not entirely low-level) and high-throughput GC.
Interesting example of this applied in practice is Garnet[0]/FASTER[1]. Keep in mind that its codebase still consist of un-idiomatic C# and you can do way better by further simplification, but it already does the job well enough.
[0] https://github.com/microsoft/garnet
[1] https://github.com/microsoft/FASTER
- FLaNK Stack 26 February 2024
- Fast persistent recoverable log and key-value store
- GitHub - microsoft/FASTER: Fast persistent recoverable log and key-value store + cache, in C# and C++.
-
FoundationDB: A Distributed Unbundled Transactional Key Value Store
A vaguely similar project that might be of interest is: https://github.com/microsoft/FASTER
It's also an "unbundled" low-level component that one could use as the foundation for a database engine or whatever. According to Microsoft, FASTER is not just "fast", but significantly faster than even some basic in-memory data structures that ship in the .NET standard library!
The downside is that it doesn't (yet) support some more advanced features like multi-server distributed mode.
However, that relative simplicity may be preferred in some scenarios...
-
Event Sourcing
Last time i looked into it there weren't that many i could find. There is https://github.com/tikv/tikv which uses rocksdb with raft. and there is faster https://github.com/microsoft/FASTER/ .
-
Experiences with Concurrent Hash Map Libraries
you could use fasterkv https://github.com/microsoft/FASTER
-
Faster A fast concurrent persistent key-value store and log, in C# and C++
FTA, https://github.com/Microsoft/FASTER/wiki/Performance-of-FAST...
vitess
-
A MySQL compatible database engine written in pure Go
With Vitess likely merging a lot of its binaries into a single unified binary: https://github.com/vitessio/vitess/issues/7471#issuecomment-...
... it would be a wild future if Vitess replaced the underlying MySQL engine with this as long as the performance is good enough.
-
The challenges of supporting foreign key constraints
Thank you for the compliment!
We recently started adding support for CTEs in Vitess! You can check out https://github.com/vitessio/vitess/pull/14321 if you want to see some technical details of the implementation.
For now, we have added preliminary support by converting them to derived tables internally, but we believe that we need to make CTEs first-class citizens themselves of query planning. Once we make that change, we can look towards supporting recursive CTEs.
This however will take some time, but then, all good things do!
-
Vitess 18
Why would it be a Google project? https://github.com/vitessio/vitess
-
PlanetScale Scaler Pro
This is great news. I strolled around https://github.com/vitessio/vitess/issues/12967.
Are there any public discussions of more trade-offs vitess has to make to enable fks?
-
What is the best database technology to use to create a new chat app today?
MySQL + Vitess I noticed Slack gets by using MySQL because they're using Vites. From Slack's post (https://slack.engineering/scaling-datastores-at-slack-with-vitess/) it seems like they choose Vites because it facilitated a smooth transition because it's built on top of MySQL.
- Vitess – Scalable. Reliable. MySQL-Compatible. Cloud-Native. Database
-
How can I avoid duplicate API calls in a serverless infra?
This sounds very similar to the connection pooling done by vitess https://vitess.io/.
-
Scaling Databases at Activision [pdf]
https://github.com/vitessio/vitess/issues/12967
-
Want to avoid MySQL but find PlanetScale really appealing
A lot of this is possible thanks to the magic of Vitess.
-
Vitess 16
"Vitess is a database clustering system for horizontal scaling of MySQL."
https://github.com/vitessio/vitess
What are some alternatives?
libcuckoo - A high-performance, concurrent hash table
tidb - TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at : https://tidbcloud.com/free-trial
parallel-hashmap - A family of header-only, very fast and memory-friendly hashmap and btree containers.
supabase - The open source Firebase alternative.
foundationdb - FoundationDB - the open source, distributed, transactional key-value store
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
plumber - A swiss army knife CLI tool for interacting with Kafka, RabbitMQ and other messaging systems.
citus - Distributed PostgreSQL as an extension
tikv - Distributed transactional key-value database, originally created to complement TiDB
go-mysql-elasticsearch - Sync MySQL data into elasticsearch
Folly - An open-source C++ library developed and used at Facebook.
kingshard - A high-performance MySQL proxy