Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gillh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
gillh
4y ago
DoorDash team talks about types of metastable failures in microservices and how observability-based control techniques can be used to mitigate them. They introduce a project called Aperture[0] that provides techniques such as adaptive concu
62.
▲
by
gillh
4y ago
This is an area our team has been working on for the last couple of years — applying control systems principles to prevent metastable failures, overloads and so on. Blog by DoorDash team - https://doordash.engineering/2023&#
63.
▲
by
gillh
4y ago
This is exactly what the Aperture project is solving: https://github.com/fluxninja/aperture
64.
▲
Show HN: OpenAI based PR reviewer and summarizer
(github.com)
3 points
by
gillh
4y ago
|
0 comments
65.
▲
by
gillh
4y ago
New link - https://github.com/marketplace/actions/openai-based-pr-revie...
66.
▲
Show HN: ChatGPT Based PR Reviewer and Summarizer
(github.com)
4 points
by
gillh
4y ago
|
2 comments
67.
▲
by
gillh
4y ago
This ChatGPT based GitHub Action provides a summary, release notes and review of pull requests. The prompts have been tuned for concise response. To prevent excessive notifications, this action can be configured to skip adding review commen
68.
▲
by
gillh
4y ago
HN: our team has been working on an advanced API queue/load management system called Aperture[0]. It has following capabilities - 1. Limits concurrency based on latency gradient or queue depths etc. 2. Weighted fair queueing scheduler
69.
▲
by
gillh
4y ago
Service meshes make it easier to roll out advanced load management/reliability features such as prioritized load shedding, which would otherwise need to be implemented within each language/framework. For instance, Aperture[0] open
70.
▲
Reliability “Spectrum”
(docs.fluxninja.com)
3 points
by
gillh
4y ago
|
0 comments
71.
▲
by
gillh
4y ago
From the way of work document at FluxNinja[0]: Task priorities are decided based on two factors: 1. The ratio of value generated per given effort: If there are two tasks with similar value but one of them requires less effort then the one w
72.
▲
Protect Your GraphQL Services with Distributed Rate Limiter
(docs.fluxninja.com)
1 points
by
gillh
4y ago
|
0 comments
73.
▲
by
gillh
4y ago
1. It doesn't do a good job in making a backup of existing files as it's meant to be setup on a new machine. However, the setup script can be quickly modified to backup existing files. See [0]. 2. Yes, it installs required package
74.
▲
by
gillh
4y ago
At our startup (FluxNinja), we provide MacBooks and Linux Desktops (System76) to our engineering staff. We have invested in common dotfiles[0] to help them keep dev experience consistent across machines. We use chezmoi for dotfiles manageme
75.
▲
Aha moments while building a deep tech startup
(twitter.com)
1 points
by
gillh
4y ago
|
0 comments
76.
▲
by
gillh
4y ago
While we are on the topic, I would like to point out that the decoupled nature of microservices is governed by queuing theory. Microservices are especially susceptible to positive feedback loops and cascading failures. Going back to systems
77.
▲
Show HN: Reliability-as-Code Platform (Aperture)
(github.com)
2 points
by
gillh
4y ago
|
0 comments
78.
▲
Why Your Service Needs Adaptive Concurrency Limits
(docs.fluxninja.com)
2 points
by
gillh
4y ago
|
0 comments
79.
▲
Why Your Service Needs Adaptive Concurrency Limits
(docs.fluxninja.com)
4 points
by
gillh
4y ago
|
1 comments
80.
▲
by
gillh
4y ago
How do popular apps keep failures low and uptime high? The answer is concurrency limits. Learn what these are and how they prevent service failures.
81.
▲
by
gillh
4y ago
The metric and the control circuit is configurable/programmable. [1] https://github.com/fluxninja/aperture/blob/main/blueprints/b...
82.
▲
by
gillh
4y ago
You should really check out the recent Aperture[1] project on GitHub that applies all these ideas in practice to protect services from cascading failures. 1. Aperture automatically detects queue buildup based on metrics such as latency. 2.
83.
▲
by
gillh
4y ago
Anyone building web-scale apps should check out Aperture[1] - a flow control platform that dynamically adjusts concurrency limits on services when queue buildup is detected. Aperture has a weighted fair queuing scheduler that prioritizes wo
84.
▲
by
gillh
4y ago
We recently started providing standardized neovim centric dotfiles setup to developers at our startup and this setup has improved productivity quite a lot. Our neovim "distribution" is highly geared towards our tech stack (Golang
85.
▲
Show HN: Aperture Open Source Flow Control and Reliability Platform
(github.com)
6 points
by
gillh
4y ago
|
0 comments
86.
▲
Show HN: Company-wide Dotfiles
(github.com)
1 points
by
gillh
4y ago
|
0 comments
87.
▲
Show HN: Scale your APIs with Aperture flow control
(github.com)
5 points
by
gillh
4y ago
|
0 comments
88.
▲
Aperture: Scale your APIs with flow control
(techcrunch.com)
5 points
by
gillh
4y ago
|
1 comments
89.
▲
by
gillh
4y ago
Aperture — the first open-source solution that protects applications from cascading failures by applying concurrency limits.
90.
▲
Show HN: Aperture – Flow Control for Cloud Apps
(github.com)
7 points
by
gillh
4y ago
|
0 comments
More ›