Seems like we’re barking up the same tree:
back
1 comments
> 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.
After 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.