HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
fluxninja
aperture
Go2022–2024
fluxninja / aperture

aperture

Rate limiting, caching, and request prioritization for modern workloads

4Distinct people
32Mentions
0Explicit recommenders
732GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rate limiting, caching, and request prioritization for modern workloads

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month32 dated mentions

Observed mentions: 2022-09-13 19:35:28 UTC to 2024-03-01 01:03:15 UTC.

02462022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 commentsSep 20222022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20232023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC330
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC303
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC101
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC202
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC615
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC505
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC404
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC615
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC000
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC101

What Hacker News says

3 sources
gillh·Sep 15, 2022Submission

Show HN: Aperture Open Source Flow Control and Reliability Platform

Hello people of HN and fellow SREs! Over the past year, we have been building Aperture - an open-source flow control and reliability platform for cloud applications. Over the past few years, companies like LinkedIn[1], Google [2], Netflix [3], Stripe [4] have built cutting-edge flow control technologies to keep their applications reliable. Flow control is powerful because it enables graceful degradation- the ability to preserve key user experience pathways, even in the face of application failures. With Aperture project, we hope to democratize building reliable applications with effective flow control. Using Aperture’s powerful policy language, you can deploy flow control techniques such as weighted fair queuing for prioritized load-shedding and distributed rate-limiting for abuse prevention to your applications. Using modular components
Read the rest
to build policies allows you to maintain optimal user experience during traffic spikes, prevents cloud resource wastage by regulating abusive users, and ensures that new feature rollouts don’t result in accidental downtime. We are excited to release Aperture as an open source project under the AGPL v3 license and invite SREs, DevOps, enthusiasts to give the project a try. We would love to hear your feedback on Aperture and how we can improve! Github: https://github.com/fluxninja/aperture Docs: https://docs.fluxninja.com/ Announcement: https://techcrunch.com/sponsor/fluxninja/fluxninja-announces... Explainer Video: https://www.youtube.com/watch?v=sEl4SMo3KNo [1]: https://engineering.linkedin.com/blog/2022/hodor--detecting-... [2]: https://sre.google/sre-book/handling-overload/ [3]: https://netflixtechblog.com/keeping-netflix-reliable-using-p... [4]: https://stripe.com/blog/rate-limiters
6 points · Open discussion
gillh·Sep 14, 2022Submission

Show HN: Scale your APIs with Aperture flow control

Hello HN, Over the past year, we have been building Aperture - an open-source flow control and reliability platform for cloud applications. Over the past few years, companies like LinkedIn[1], Google [2], Netflix [3], Stripe [4] have built cutting-edge flow control technologies to keep their applications reliable. Flow control is powerful because it enables graceful degradation- the ability to preserve key user experience pathways, even in the face of application failures. With Aperture project, we hope to democratize building reliable applications with effective flow control. Aperture enables flow control through Aperture Agents and an Aperture Controller. Aperture Agents live next to your service instances as a sidecar and provide flow control components such as a weighted fair queuing scheduler for prioritized load-shedding and a distr
Read the rest
ibuted rate-limiter for abuse prevention. A flow is the fundamental unit of work from the perspective of an Aperture Agent. It could be an API call, a feature, or even a database query. The Aperture Controller is powered by always-on, dataflow-driven policies that continuously track deviations from SLOs and calculate recovery or escalation actions. The policies running in the Controller are expressed as circuits, similar to circuit networks in the game Factorio[5]. You can deploy Aperture into your service instances through Service Mesh (using Envoy) or Aperture SDKs. We are excited to release Aperture as an open source project under the AGPL v3 license, and invite SREs, DevOps & enthusiasts to give the project a try. We would love to hear your feedback on Aperture and how we can improve! GitHub: https://github.com/fluxninja/aperture Docs: https://docs.fluxninja.com/ Announcement: https://techcrunch.com/sponsor/fluxninja/fluxninja-announces... Explainer Video: https://www.youtube.com/watch?v=sEl4SMo3KNo [1]: https://engineering.linkedin.com/blog/2022/hodor--detecting-... [2]: https://sre.google/sre-book/handling-overload/ [3]: https://netflixtechblog.com/keeping-netflix-reliable-using-p... [4]: https://stripe.com/blog/rate-limiters [5]: https://wiki.factorio.com/Circuit_network
5 points · Open discussion
gillh·Sep 13, 2022Submission

Show HN: Aperture – Flow Control for Cloud Apps

Hello HN, Over the past year, we have been building Aperture - an open-source flow control and reliability platform for cloud applications. Over the past few years, companies like LinkedIn[1], Google [2], Netflix [3], Stripe [4] have built cutting-edge flow control technologies to keep their applications reliable. Flow control is powerful because it enables graceful degradation- the ability to preserve key user experience pathways, even in the face of application failures. With Aperture project, we hope to democratize building reliable applications with effective flow control. Aperture enables flow control through Aperture Agents and an Aperture Controller. Aperture Agents live next to your service instances as a sidecar and provide flow control components such as a weighted fair queuing scheduler for prioritized load-shedding and a distr
Read the rest
ibuted rate-limiter for abuse prevention. A flow is the fundamental unit of work from the perspective of an Aperture Agent. It could be an API call, a feature, or even a database query. The Aperture Controller is powered by always-on, dataflow-driven policies that continuously track deviations from SLOs and calculate recovery or escalation actions. The policies running in the Controller are expressed as circuits, similar to circuit networks in the game Factorio[5]. You can deploy Aperture into your service instances through Service Mesh (using Envoy) or Aperture SDKs. We are excited to release Aperture as an open source project under the AGPL v3 license, and invite SREs, DevOps & enthusiasts to give the project a try. We would love to hear your feedback on Aperture and how we can improve! GitHub: https://github.com/fluxninja/aperture Docs: https://docs.fluxninja.com/ Announcement: https://techcrunch.com/sponsor/fluxninja/fluxninja-announces... Explainer Video: https://www.youtube.com/watch?v=sEl4SMo3KNo [1]: https://engineering.linkedin.com/blog/2022/hodor--detecting-... [2]: https://sre.google/sre-book/handling-overload/ [3]: https://netflixtechblog.com/keeping-netflix-reliable-using-p... [4]: https://stripe.com/blog/rate-limiters [5]: https://wiki.factorio.com/Circuit_network
7 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.