aperture
syncthing
aperture | syncthing | |
---|---|---|
28 | 130 | |
590 | 59,621 | |
1.7% | 1.1% | |
9.8 | 9.4 | |
3 days ago | 2 days ago | |
Go | Go | |
Apache License 2.0 | Mozilla Public License 2.0 |
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
syncthing
-
Platform issues which disadvantage Firefox compared to first-party browsers
My biggest gripe with Firefox on Android is that sometimes I enter a domain in the address bar, press enter and nothing happens.
This behaviour seems to be erratic and only affects a few websites, such as https://forum.syncthing.net.
Closing the tab or using a different one doesn't solve the problem. I need to force close the app to fix this.
-
Why are Apple Silicon VMs so different?
Syncthing has had on their roadmap for 9.5 years to support iOS but hasn’t due to lack of interest by the developers to devote the time to make it.
https://github.com/syncthing/syncthing/issues/102
macOS is supported though.
And Syncthing via 3rd parties does support iOS.
-
Syncthing problems
I haven't been able to access https://docs.syncthing.net or https://forum.syncthing.net/ but I was able to access some of the docs via github. I think I've set it up according to the docs. The logs contain lots of messages like:
-
iCloud Drive silently deletes your content
Malware built into iOS makes it impossible to install Syncthing[0], which is a problem for most of the people who use iCloud tp sync their files.
[0] https://github.com/syncthing/syncthing/issues/102
-
Veilid is an open-source, P2P, mobile-first, networked application framework
https://github.com/syncthing/syncthing/issues/8423
-
Why is There no Official Flatpak Version?
They seem to have chosen Docker instead of Flatpak. You can get it with Docker by running:
-
The holy grail of note-taking: Private data, efficient methodology and P2P encrypted sync across all your devices
syncthing is fully open sourced and distributed under MPL-2 licenses, while dropbox is not!
- Keep SD Cards in sync
- Continuous File Sync Written in Go Trending on GitHub
-
Syncthing: A continuous file synchronization program
You could try to force QUIC which should handle latency a bit better. The priority of TCP/QUIC will be configurable with the upcoming v1.23.5 release:
https://github.com/syncthing/syncthing/pull/8868
What are some alternatives?
rules_jsonnet - Jsonnet rules for Bazel
Nextcloud - ☁️ Nextcloud server, a safe home for all your data
slo-exporter - Slo-exporter computes standardized SLI and SLO metrics based on events coming from various data sources.
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
awesome-sre-tools - A curated list of Site Reliability and Production Engineering Tools
Samba - https://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub)
now-boltwall - Vercel lambda deployment for a Nodejs Lightning-powered Paywall
Seafile - High performance file syncing and sharing, with also Markdown WYSIWYG editing, Wiki, file label and other knowledge management features.
ai-pr-reviewer - AI-based Pull Request Summarizer and Reviewer with Chat Capabilities.
Git Annex
etleneum - the centralized smart contract platform
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]