4 ms·
Seems like we’re barking up the same tree: https://github.com/proxylity/raptor https://github.com/proxylity/raptor
by mlhpdx 4mo ago
Seems like we’re barking up the same tree:
https://github.com/proxylity/raptor https://github.com/proxylity/raptor
- eventualcomp 4mo ago> Perhaps most importantly, it does so using a tiny fraction of the CPU time, saving energy and keeping our datacenters (and planet) a little cooler. But then: > A decoder backend on AWS (SQS + Lambda + DynamoDB + S3) reassembles objects from incoming encoded packets delivered via Proxylity UDP Gateway. :( those microservice invocation will burn up the DC more. The real sell looks like offloading s3 upload latency.
- mlhpdx 4mo agoAfter having used it a while I tend to agree — the snappy send time is such a nice change. Maybe at some point S3 will have a native implementation of something like this.