skytable
tokio
Our great sponsors
skytable | tokio | |
---|---|---|
21 | 196 | |
2,249 | 24,610 | |
11.1% | 2.5% | |
9.2 | 9.5 | |
6 days ago | 7 days ago | |
Rust | Rust | |
GNU Affero General Public License v3.0 | MIT License |
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.
skytable
-
Show HN: Skytable's new NoSQL engine BlueQL with injection safety, improved perf
Hey HN!
I've been working on Skytable since 2020 and after several iterations from a simple K/V store, we've walked the path to this release. The goal of Skytable is to deliver a solid foundation for building data intensive applications.
Skytable's primary goal is performance and scale. Even with a query language it can outperform K/V stores which use simple commands (benchmarks will be shared in another post).
Several implementations in Skytable (especially around query evaluation and execution) are fundamentally different from SQL and even NoSQL counterparts and there are some entirely new concepts which might make it a little hard to grasp.
BlueQL is a very important part of Skytable and it employs some interesting concepts to try and reduce the surface for injection attacks and tries to be a modern and secure alternative to SQL.
- Source code: https://github.com/skytable/skytable
-
Updated: Understanding the working of Skytable's NoSQL engine
For those who were looking for the source code, here's the link: https://github.com/skytable/skytable
-
Skytable’s new NoSQL engine released: BlueQL, injection protection, collections and performance improvements
Link to source code: https://github.com/skytable/skytable
Here are some quick links: - Source code: https://github.com/skytable/skytable - Rust driver: https://github.com/skytable/client-rust
- Skytable
- Skytable Octave was just released with BlueQL, advanced data modeling, complex collections and rich querying ✨🚀🎱. Tell us what you think!
- Skytable NoSQL Database: Even with BlueQL, Skytable Outperforms Redis and KeyDB
-
The first version of Redis, written in Tcl
I think this is relevant... These are 3 OSS databases that can be an alternative to Redis:
- KeyDB: https://github.com/snapchat/keydb
- Dragonfly: https://github.com/dragonflydb/dragonfly
- Skytable: https://github.com/skytable/skytable
I have used keyDB before. The raft consensus makes building an HA Redis easy.
-
Skytable PHP Client
:) in fact, I copied the definition from the project page and Skytable is not finished project yet. You can see here, the real time features in the road map. https://github.com/skytable/skytable/issues/203
- skytable / skytable :
tokio
-
On Implementation of Distributed Protocols
Being able to control nondeterminism is particularly useful for testing and debugging. This allows creating reproducible test environments, as well as discrete-event simulation for faster-than-real-time simulation of time delays. For example, Cardano uses a simulation environment for the IO monad that closely follows core Haskell packages; Sui has a simulator based on madsim that provides an API-compatible replacement for the Tokio runtime and intercepts various POSIX API calls in order to enforce determinism. Both allow running the same code in production as in the simulator for testing.
-
I pre-released my project "json-responder" written in Rust
tokio / hyper / toml / serde / serde_json / json5 / console
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
tokio - An asynchronous runtime for Rust
-
Top 10 Rusty Repositories for you to start your Open Source Journey
3. Tokio
-
API Gateway, Lambda, DynamoDB and Rust
The AWS SDK makes use of the async capabilities in the Tokio library. So when you see async in front of a fn that function is capable of executing asynchronously.
-
The More You Gno: Gno.land Monthly Updates - 6
Petar is also looking at implementing concurrency the way it is in Go to have a fully functional virtual machine as it is in the spec. This would likely attract more external contributors to developing the VM. One advantage of Rust is that, with the concurrency model, there is already an extensive library called Tokio which he can use. Petar stresses that this isn’t easy, but he believes it’s achievable, at least as a research topic around determinism and concurrency.
-
Consuming an SQS Event with Lambda and Rust
Another thing to point out is that async is a thing in Rust. I'm not going to begin to dive into this paradigm in this article, but know it's handled by the awesome Tokio framework.
-
netcrab: a networking tool
So I started by using Tokio, a popular async runtime. The docs and samples helped me get a simple outbound TCP connection working. The Rust async book also had a lot of good explanations, both practical and digging into the details of what a runtime does.
-
Thread-per-Core
Regarding the quote:
> The Original Sin of Rust async programming is making it multi-threaded by default. If premature optimization is the root of all evil, this is the mother of all premature optimizations, and it curses all your code with the unholy Send + 'static, or worse yet Send + Sync + 'static, which just kills all the joy of actually writing Rust.
Agree about the melodramatic tone. I also don't think removing the Send + Sync really makes that big a difference. It's the 'static that bothers me the most. I want scoped concurrency. Something like <https://github.com/tokio-rs/tokio/issues/2596>.
Another thing I really hate about Rust async right now is the poor instrumentation. I'm having a production problem at work right now in which some tasks just get stuck. I wish I could do the equivalent of `gdb; thread apply all bt`. Looking forward to <https://github.com/tokio-rs/tokio/issues/5638> landing at least. It exists right now but is experimental and in my experience sometimes panics. I'm actually writing a PR today to at least use the experimental version on SIGTERM to see what's going on, on the theory that if it crashes oh well, we're shutting down anyway.
Neither of these complaints would be addressed by taking away work stealing. In fact, I could keep doing down my list, and taking away work stealing wouldn't really help with much of anything.
-
PHP-Tokio – Use any async Rust library from PHP
The PHP <-> Rust bindings are provided by https://github.com/Nicelocal/ext-php-rs/ (our fork of https://github.com/davidcole1340/ext-php-rs with a bunch of UX improvements :).
php-tokio's integrates the https://revolt.run event loop with the https://tokio.rs event loop; async functionality is provided by the two event loops, in combination with PHP fibers through revolt's suspension API (I could've directly used the PHP Fiber API to provide coroutine suspension, but it was a tad easier with revolt's suspension API (https://revolt.run/fibers), since it also handles the base case of suspension in the main fiber).
What are some alternatives?
ArangoDB - 🥑 ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.
async-std - Async version of the Rust standard library
KeyDB - A Multithreaded Fork of Redis
Rocket - A web framework for Rust.
dragonfly - A modern replacement for Redis and Memcached
hyper - An HTTP library for Rust
calligrapher-ai - Handwriting Synthesis with RNNs ✍🏻
futures-rs - Zero-cost asynchronous programming in Rust
oxigraph - SPARQL graph database
smol - A small and fast async runtime for Rust
sky-benches - Attempts at benchmarking Skytable with the others to see where we stand
rayon - Rayon: A data parallelism library for Rust