aperture

README

🥷 FluxNinja Aperture

Aperture is an observability-driven load management platform for modern cloud applications.

⚙️ Features

• Adaptive service protection: Enhance resource utilization and safeguard against abrupt service overloads with an intelligent queue at the entry point of services. This queue dynamically adjusts the rate of requests based on live service health, thereby mitigating potential service disruptions and ensuring optimal performance under all load conditions.
• Global quota management: Maintain compliance with external API quotas with a global token bucket and smart request queuing. This feature regulates requests aimed at external services, ensuring that the usage remains within prescribed rate limits and avoids penalties or additional costs.
• Workload prioritization: Safeguard crucial user experience pathways and ensure prioritized access to external APIs even during high-load conditions by strategically prioritizing workloads. This is achieved through the use of declarative policies that label and prioritize workload requests, such as API calls. By employing weighted fair queuing for scheduling, Aperture ensures a fair distribution of resources that aligns with the business value and urgency of requests.
• Load-based auto-scaling: Eliminate the need for costly over-provisioning and enhance efficiency with Aperture's load-based auto-scaling. Aperture's policies are expressed as circuit graphs that continuously track deviations from service-level objectives and calculate recovery or escalation actions. Auto-scaling can be implemented as an escalation that triggers based on load throttling signal.
• Distributed rate-limiting: Safeguard APIs from potential abuse with Aperture's high-performance, distributed rate limiter. This feature enforces per-key limits based on fine-grained labels, ensuring precise control and prevention of excessive usage.
• Automated load ramping: Ensure a safe and gradual increment of load to new features or API endpoints. Aperture continuously monitors for potential performance issues, offering an automatic response mechanism to dial back load in case of a performance regression. This proactive approach minimizes service disruptions and maintains consistent performance, even when rolling out new features.

🏗️ Architecture

• 🚦 Aperture Agents are typically deployed next to the services and provide high-performance load management capabilities. They are responsible for scheduling and rate-limiting incoming requests based on the policies defined in the Aperture Controller. In addition, they also collect service health and flow metrics.

• 🤖 Aperture Controller executes observability-driven control policies and configures Aperture Agents. The control policies are expressed as circuit graphs consisting of interconnected signal processing blocks. The Aperture policies provide a programmable way to tailor sophisticated control policies to match any application's needs.

🏁 Getting Started

🎮 Playground

To try Aperture in a local Kubernetes environment, refer to Playground docs.

🏎️ Installation

To install the Aperture system, please follow the Installation guide.

📖 Use Cases

Learn about various use cases of Apertures in the Applying Policies section.

🎥 Videos

• Chaos Carnival 2023-Graceful Degradation:Keeping The Lights On When Everything Goes Wrong
• Graceful Degradation: When All Goes Wrong | Tanveer Gill | Conf42 Chaos Engineering 2023
• How Concurrency Limits Help Protect Against Cascading Failures
• Build Indestructible Applications with Aperture Flow Control

👷 Contributing

Reporting bugs helps us improve Aperture to be more reliable and user-friendly. Please make sure to include all the required information to reproduce and understand the bug you are reporting. Follow helper questions in the bug report template to make it easier. If you see a way to improve Aperture, use the feature request template to create an issue.

To contribute code, please read the Contribution guide.