edgedns
nench
Our great sponsors
edgedns | nench | |
---|---|---|
2 | 1 | |
498 | 825 | |
- | - | |
0.0 | 0.0 | |
over 3 years ago | over 4 years ago | |
Rust | Shell | |
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.
nench
-
How to build a CDN (1/3): introduction and basic components
Virtual vs. physical server — this is a rather controversial topic and it is not appropriate to generalize it. If the economy allows, choose physical servers for critical servers, even if only those from the basic menu. Redundant disks are a must, ideally with redundant power supply. With a physical server, you usually get a 1 Gbps uplink and a direct physical connection directly to the ToR switch. There is a much lower chance that you will struggle with sharing CPU and IO or connectivity on a physical hypervisor running hundreds, or dozens of virtual servers at best. If you’re lucky, they have a shared “tube” of * × 10 Gbit, or worse, they have 1 Gbit. With authenticated providers you don’t even have to worry about virtual servers, just watch the aggregation and performance (eg benchmark nench). Over time, the collected metrics will also tell you a lot, especially for redundant PoPs that will handle ± the same traffic (DNS round-robin). As a result, we have very quickly detected very aggressive CPU throttling or volatile IO performance at some providers.
What are some alternatives?
rust-memcache - memcache client for rust
moka - A high performance concurrent caching library for Rust
dns-over-wikipedia - Redirect `.idk` domains using Wikipedia
cachepot - cachepot is `sccache` with extra sec, which in turn is `ccache` with cloud storage
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
trust-dns - A Rust based DNS client, server, and resolver [Moved to: https://github.com/hickory-dns/hickory-dns]
pandit - My Final Year Project. A distributed proxy that converts applications into gRPC Services. Provides powerful user-defined caching strategies.
ipad-target.py - Checks Target.com for iPad inventory
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
pyp2p