aperture
snapcraft
aperture | snapcraft | |
---|---|---|
28 | 112 | |
590 | 1,136 | |
1.7% | 0.3% | |
9.8 | 9.6 | |
3 days ago | about 9 hours ago | |
Go | Python | |
Apache License 2.0 | GNU General Public License v3.0 only |
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
snapcraft
-
Operating System Wars, what is the best operating system for programming. ⚔️
Back in the day, I used snapd, which is similar to Mac's Homebrew.
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Setting Up for Java on Linux.
My personal favourite IDE for java is Intellej Idea. Apart from not demanding the extra extension, It was designed special for Java and Java related languages so it runs java smoothly with great compilation time. so lets install it. Make sure you have snap before installing it
-
Why is Linux so hard and anti GUI?
Linux Mints App Store is full of GUI programs, Snap Store ist full of it, Flathub is full of it.
-
This might seem dumb but where tf does snap put the actual files and stuff?
You are being lazy. But I recommend bringing your ass directly to snapcraft.io and reading those documents in the Learn section!!
- Just set up Ubuntu 22.04, looking for software recommendations
-
[seriously] Why do people hate snaps?
https://github.com/snapcore/snapcraft - not sure, but looks like a building tools for snaps
- Flutter 3 on Devuan 4: 始め方
-
Flutter 3 on Devuan 4: Getting started
Besides, there may be other ways to install them, although there doesn't seem no such Flatpak packages in Flathub. For example, some senerio to use some release channel or Docker / Podman. Additionally, when you use a different Linux distro where systemd is adopted and therefore can do Snaps (Snapd), you have another possibility.
- Android Studio on Devuan 4: インストール
What are some alternatives?
rules_jsonnet - Jsonnet rules for Bazel
com.spotify.Client
slo-exporter - Slo-exporter computes standardized SLI and SLO metrics based on events coming from various data sources.
input-remapper - 🎮 ⌨ An easy to use tool to change the behaviour of your input devices.
awesome-sre-tools - A curated list of Site Reliability and Production Engineering Tools
flathub - Pull requests for new applications to be added
now-boltwall - Vercel lambda deployment for a Nodejs Lightning-powered Paywall
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
ai-pr-reviewer - AI-based Pull Request Summarizer and Reviewer with Chat Capabilities.
express-vpn-gui - ExpressVPN GUI for Linux
etleneum - the centralized smart contract platform
flatpak - Linux application sandboxing and distribution framework