aperture
ngrok
aperture | ngrok | |
---|---|---|
28 | 12 | |
590 | 23,938 | |
1.7% | - | |
9.8 | 3.7 | |
3 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
aperture
-
Defcon: Meta's system for preventing overload with graceful feature degradation
Anyone interested in load shedding and graceful degradation with request prioritization should check out the Aperture OSS project.
https://github.com/fluxninja/aperture
-
Queues Don't Fix Overload
I agree that queues can problem especially when misconfigured. But some amount of queuing is necessary, to absorb short spikes in demand vs capacity. Also, queues can be helpful to re-order requests based on criticality which won't be possible with zero queue size - in which case we have to immediately drop a request or admit it without considering it's priority.
I think it is beneficial to re-think how we tune queues. Instead of setting a queue size, we should be tuning the max permissible latency in the queue which is what a request timeout actually is. That way, you stay within the acceptable response time SLA while keeping only the serve-able requests in the queue.
Aperture, an open-source load management platform took this approach. Each request specifies a timeout for which it is willing to stay in the queue. And weighted fair queuing scheduler then allocates the capacity (a request quota or max number of in-flight request) across requests based on the priority and tokens (request heaviness) of each request.
Read more about the WFQ scheduler in Aperture: https://docs.fluxninja.com/concepts/scheduler
Link to Aperture's GitHub: https://github.com/fluxninja/aperture
Would love to hear your thoughts on our approach!
-
Kelsey Hightower's Twitter Spaces on Rate Limits & Flow Control
For those keen to dive deeper, I highly recommend exploring both the Twitter Space and Aperture: [Twitter Spaces]: https://twitter.com/kelseyhightower/status/1689355284802629633?s=20 [GitHub repo]: https://github.com/fluxninja/aperture
-
Graceful Behavior at Capacity
Very interesting blog post! Our team has been working intensively in this area for the last couple of years - flow control, load shedding, controllability (PID control), and so on.
We have open-sourced our work at - https://github.com/fluxninja/aperture
We would love feedback from folks reading this blog post!
Disclaimer: I am one of the co-authors of the Aperture project. There are several interesting ideas we have built into this project and I will be happy to dive into the technical details as well.
-
Why Adaptive Rate Limiting Is a Game-Changer
It's a blog on an open-source project that precisely tells you how to implement adaptive rate limiting.
Just click around a bit:
- https://github.com/fluxninja/aperture
- https://docs.fluxninja.com/use-cases/adaptive-service-protec...
Note: I am one of the authors' of this project.
-
Show HN: Review GitHub PRs with AI/LLMs
At the time of writing, the first sample image on that page is this:
https://coderabbit.ai/assets/section-1-f9a48066.png
which recommends adding a "maxIterations" counter to the "for len(executedComponents) ..." loop here:
https://github.com/fluxninja/aperture/blob/26e00ea818c7c28da...
HOWEVER
- the review has failed to notice the logic using "numExecutedBefore" (around line 377) that already prevents the specific bug it is suggesting a fix for
- the suggested change decrements "maxIterations" inside the "for ... range circuit.components {" loop which means it isn't counting iterations, it's counting components
This kind of suggestion is particularly nasty because it's unlikely that the test suite populates enough components to hit "maxIterations" - so an inattentive reader could accept it, get a green build, and then deploy a production bug!
-
June 25th, 2023 Deno Deploy Postmortem
The need an adaptive protection system like Aperture[0] to mitigate overloads.
[0]: https://github.com/fluxninja/aperture
-
Jsonnet – The Data Templating Language
It’s customized to our policy spec. But you can learn from this and adapt it to your spec.
https://github.com/fluxninja/aperture/blob/main/scripts/json...
- Show HN: Aperture – Unified Reliability Management for Microservices
- Failure Mitigation for Microservices: An Intro to Aperture
ngrok
-
List of ngrok/Cloudflare Tunnel alternatives and other tunneling software and services. Focus on self-hosting.
ngrok 1.0 - Original version of ngrok. No longer developed in favor of the commercial 2.0 version.
-
Portr – open-source ngrok alternative designed for teams
Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:
OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...
Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...
ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...
I'll see that OG localtunnel gets added to the list for posterity.
[0]: https://github.com/anderspitman/awesome-tunneling
[1]: https://github.com/localtunnel/localtunnel
-
What is the coolest Go open source projects you have seen?
ngrok
-
ngrok open source alternative for SSH tunnelling?
if you're worried about the line "ngrok captures and analyzes all traffic over the tunnel for later inspection and replay" in https://github.com/inconshreveable/ngrok, I'd say that's a valid concern but not for ssh if you make sure the client knows what the host key is and does not accept a different one
-
Alternative to ngrok's web interface that doesn't require a public URL?
Looks like it's open source so it could be just a fork away https://github.com/inconshreveable/ngrok
-
Building a HTTP Tunnel with WebSocket and Node.JS
To get a fix domain, we can deploy HTTP tunnel in our own server. ngrok also provides an open source version for server side deployment. But it is old 1.x version and not recommended to deploy at production with some serious reliability issues.
-
Real-time logs sharing by just piping stdout (my first golang project)
I ended up inspired by ngork structure here: https://github.com/inconshreveable/ngrok it doesn't really work well with go modules, since i will end up running project like this:
-
I'm losing my mind (help post)
Maybe https://github.com/inconshreveable/ngrok/issues/408
-
Reverse HTTP proxy over WebSocket in Go (Part 1)
In Go, inconshreveable/ngrok and coyove/goflyway is well known, especially ngrok is popular among developers as a SaaS service.
- 15 Command Line Tools which Spark Joy in Your Terminal
What are some alternatives?
rules_jsonnet - Jsonnet rules for Bazel
pdfcpu - A PDF processor written in Go.
slo-exporter - Slo-exporter computes standardized SLI and SLO metrics based on events coming from various data sources.
go-cron - A simple Cron library for go that can execute closures or functions at varying intervals, from once a second to once a year on a specific date and time. Primarily for web applications and long running daemons.
awesome-sre-tools - A curated list of Site Reliability and Production Engineering Tools
go-torch
now-boltwall - Vercel lambda deployment for a Nodejs Lightning-powered Paywall
fzf - :cherry_blossom: A command-line fuzzy finder
ai-pr-reviewer - AI-based Pull Request Summarizer and Reviewer with Chat Capabilities.
hub - A command-line tool that makes git easier to use with GitHub.
etleneum - the centralized smart contract platform
excelize - Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets