skytable
Memcached
Our great sponsors
skytable | Memcached | |
---|---|---|
21 | 54 | |
2,098 | 13,113 | |
5.7% | 1.0% | |
9.2 | 8.5 | |
15 days ago | 1 day ago | |
Rust | C | |
GNU Affero General Public License v3.0 | BSD 3-clause "New" or "Revised" 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
-
Skytable’s new NoSQL engine released: BlueQL, injection protection, collections and performance improvements
Here are some quick links: - Source code: https://github.com/skytable/skytable - Rust driver: https://github.com/skytable/client-rust
- 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
-
Commit 1 to 1000 and beyond: Two years of maintaining an open-source project
Back in June 2020, I started writing what is now known as Skytable, a NoSQL database project. Ever since, I have been maintaining Skytable, mostly in my free time and have recently been spending a lot of time on it. Here's a little story on my two years of experience in maintaining an open-source project: what it's like, the highs and lows and the future.
- So, you call yourself the fastest key/value store? It's 5X, 10x and 25X faster
-
Jotsy: A self-hosted notes app powered by Skytable, Axum and Tokio
I'm delighted to release Jotsy — a self-hosted, free and open-source (Apache-2.0) note taking app, built with Skytable, Axum and Tokio. The most important goal of Jotsy is to be simple and focus on the most important thing, notemaking.
-
NoSQL and Key-Value storage systems based on Rust (Redis and Tarantool replacements in Rust)
Skytable — A multi-model NoSQL database
-
What are you using Rust for?
Well, we're building the Skytable database with it.
Memcached
-
How to choose the right type of database
Memcached: A simple, open-source, distributed memory object caching system primarily used for caching strings. Best suited for lightweight, non-persistent caching needs.
-
Sieve is simpler than LRU
Oh, thank you! I didn't realize that LRU Maintainer Thread was more than an expiration reaper. When it was first being introduced that was its first responsibility as lazy expiration removal by size eviction meant dead entries wasted capacity. It was all work in progress when I had read about it [1] and talked to dormando, so it got fuzzy. The compat code [2, 3] might have also thrown me off if I only looked at the setting and not the usage. Its a neat variant to all of these ideas.
-
A Developer's Journal: Simplifying the Twelve-Factor App
stores session state in a session store like Memcached or Redis.
-
Django Caching 101: Understanding the Basics and Beyond
Django supports using Memcached as a cache backend. Memcached is a high-performance, distributed memory caching system that can be used to store cached data across multiple servers.
-
Node.js server-side authentication: Tokens vs. JWT
In server-side authentication, the session state is stored on the server-side, which can be scaled horizontally across multiple servers using tools like Redis or Memcached.
-
Scaling moderate sized websites
Caching - while it's not possible to cache everything, there's always a large percentage of your website / app that can be cached for an hour or ten minutes or 1 day etc... - all depends on the type of content but the longer you can cache for without negatively effecting content quality - the better. A good caching server example would be redis : https://redis.io/ or https://memcached.org/
-
Why do people curse JS so much, but also say it's better than Python
If you really care about optimising this, you need, as other traders pointed out, a cache. Caches are a way of ensuring that the data you query stays in memory on a separate machine so you don't have the delay to disk & to commit. Things like memcached are created for this exact purpose. If you care about optimisation, look into it and other options. This is not a simple problem. Distributed systems like these are a whole area of work and research, so it won't be as simple as just swapping a DB, but if you care about performance, this is the path you have to go down eventually.
-
Web resource caching: Server-side
A couple of dedicated server-side resource caching solutions have emerged over the years: Memcached, Varnish, Squid, etc. Other solutions are less focused on web resource caching and more generic, e.g., Redis or Hazelcast.
-
jwz: Mastodon stampede
MEMCACHED
-
How to Scale Ruby on Rails Applications
Now that we know what to cache and the techniques Rails provides to store things in the cache, the next logical question is — where do we cache this data? Rails comes with several in-built cache store adapters. The most popular cache stores for production use cases are Redis and Memcached. There are a couple of other options as well — the file store and memory store. A full discussion of these stores can be found in the post Rails' built-in cache stores: an overview.
What are some alternatives?
Varnish - The project homepage
node-cache - A simple in-memory cache for nodejs
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.
KeyDB - A Multithreaded Fork of Redis
dragonfly - A modern replacement for Redis and Memcached
node-cache - a node internal (in-memory) caching module
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
calligrapher-ai - Handwriting Synthesis with RNNs ✍🏻
oxigraph - SPARQL graph database
SSDB - SSDB - A fast NoSQL database, an alternative to Redis