edgedns
moka
Our great sponsors
edgedns | moka | |
---|---|---|
2 | 4 | |
498 | 1,345 | |
- | 7.7% | |
0.0 | 9.3 | |
over 3 years ago | 10 days ago | |
Rust | Rust | |
ISC 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.
edgedns
- Ask HN: What side projects landed you a job?
-
How to build a CDN (1/3): introduction and basic components
For the biggest pioneers, there is also a variant to build your own GeoDNS service with your own name servers. But for this to make sense and real value, anycast IP addresses would be needed. Also a number of other reliable servers around the world with DDoS protection and then understand, select and adapt eg EdgeDNS or Czech Knot DNS (which also uses Cloudflare). However, commercial GeoDNS services are relatively cheap and reliable, so we can’t imagine an ROI that would make sense with our own small, non-commercial DNS solution.
moka
-
Python deserves a good in-memory cache library!
If you know Caffeine(Java)/Ristretto(Go)/Moka(Rust), you know what Theine is. Python deserves a good in-memory cache library.
-
caching, asynchronous, request deduplication - deduplicate 0.3.1
Thanks for the feedback. I am aware of Moka. We used it on a work project but stopped because we had a couple of issues with it. The main one was: https://github.com/moka-rs/moka/issues/154 which I think is fixed now and a smaller issue which was caused by the Quanta crate crashing on AMD chips (also fixed).
-
Writing a concurrent LRU cache
Ya, I saw concache but I looked into it and it doesn't implement what is needed. Each bucket has its own linked-list backing (hence "lock-free linked list buckets"). An LRU needs each value in each bucket to be part of one linked list I believe. After posting this I realized my line of research was failing because it was state of the art five years ago. Caffeine replaced `concurrentlinkedhashmap` in the java world (by the same author). A rust version of that is Moka. These are much more complicated than a concurrent LRU but faster (aka more state of the art). Another rust crate is Stretto which is a port of dgraph's Ristretto (in go). The question becomes is it worth it to essentially port `concurrentlinkedhashmap` to have a great concurrent LRU when there are more state of the art caches out there.
-
Stretto - a thread-safe, high-performance, high hit-ratio cache.
How does it compare to https://github.com/moka-rs/moka ?
What are some alternatives?
rust-memcache - memcache client for rust
stretto - Stretto is a Rust implementation for Dgraph's ristretto (https://github.com/dgraph-io/ristretto). A high performance memory-bound Rust cache.
dns-over-wikipedia - Redirect `.idk` domains using Wikipedia
ristretto - A high performance memory-bound Go cache
cachepot - cachepot is `sccache` with extra sec, which in turn is `ccache` with cloud storage
dashmap - Blazing fast concurrent HashMap for Rust.
vodo - A primitive DNS server written in Rust for fun.
hitbox - A high-performance caching framework suitable for single-machine and for distributed applications in Rust
Stretto - Beautiful web-based music player
nench - VPS benchmark script — based on the popular bench.sh, plus CPU and ioping tests, and dual-stack IPv4 and v6 speedtests by default
concurrentlinkedhashmap - A ConcurrentLinkedHashMap for Java