Live data from Hacker News

The fastest de-referer service... with AWS Global Accelerator

lifeofguenter.de

31–40 of 79 posts

Re: The fastest de-referer service... with AWS Global Accelerator

#31
post #15

Full disclosure, I work at Fly.io now. This exact setup is easier on Fly.io - our proxy layer runs in 20 regions worldwide with anycast, so your requests hit the nearest region and quickly terminate TLS there. You can also run any Docker container, and either choose regions to run them in, or just set the min/max and ask us to start and stop containers in whichever region has demand, so your deployment follows the su…

I really like Fly and would love to move some side project workloads to it, the only thing holding me back is the Postgres product which seems to be a little bit 'not ready for production'. I'm referring to point-in-time recovery and ease of backup restoration mostly.

The product looks too good to be true, and when you dig into a little deeper it seems like it isn't totally 100%.

Amazon RDS is something that I really trust, but I didn't get the same vibe looking at Fly Postgres.

Re: The fastest de-referer service... with AWS Global Accelerator

#32

I read the first six paragraphs and still really had no idea what this is talking about. Can anyone help me understand?

The author likes AWS Global Accelerator. The author likes GA mainly because it uses BGP anycast, which means that the packets drop into AWS' network at the closest AWS point-of-presence, instead of traversing the internet. The author's experience is that this feature of GA, when combined with always-on VMs that do not need to cold start, provides him low latency for a particular service he is running.

The author also mentions Cloudflare and Google App Engine, but rejects these because on those services he chose to use the lambda-like compute functionality and wasn't prepared for the cold starts. He doesn't appear to have tried using Lambda on AWS, or dedicated VMs with Google. Thus it is a slightly apples-to-oranges comparison.

Re: The fastest de-referer service... with AWS Global Accelerator

#33
post #12

Using a Rwandan TLD negates pretty much all the effort in finding the fastest provider. No glue records and an unresponsive TLD nameserver translates into 100+ms for the initial DNS lookup (likely the only one that matters for such a service).

If you don't know, DNS are cached at multiple layers, including ISP.

This is technically correct but don’t rely on caching to solve this problem. Unless you’re getting a ton of widespread traffic you’ll probably be getting more cache misses than you expect - every time I did client-side monitoring, the DNS 90th percentile was quite notably higher than the 50th.

Re: The fastest de-referer service... with AWS Global Accelerator

#34

I read the first six paragraphs and still really had no idea what this is talking about. Can anyone help me understand?

The author likes AWS Global Accelerator. The author likes GA mainly because it uses BGP anycast, which means that the packets drop into AWS' network at the closest AWS point-of-presence, instead of traversing the internet. The author's experience is that this feature of GA, when combined with always-on VMs that do not need to cold start, provides him low latency for a particular service he is running. The author also…

I opened a request on GitHub that Global Accelerator support AWS AppRunner (persistent containers in Fargate VMs with HTTP/S gateway) as an endpoint. That'd cover all of OP's usecases (and the one that I also have): https://github.com/aws/apprunner-roadmap/issues/83

Re: The fastest de-referer service... with AWS Global Accelerator

#36

I didn't know this! How is this different from AWS CloudFront?

Cloudfront caches content at edge locations near users whilst Accelerator routes requests to the nearest endpoint to the user.

If I am understanding it correctly, Cloudfront can use Accelerator to find the nearest edge location to cache, right?

Re: The fastest de-referer service... with AWS Global Accelerator

#37
> ”Cloudflare will not serve traffic from all edge locations, especially Australia is hit hard.”

I’ve read a few (dated) posts about bandwidth costs being extreme in Australia and Cloudflare would route around it, causing higher latency in that region.

Is that still the case though?

Re: The fastest de-referer service... with AWS Global Accelerator

#38
post #6

Earlier quoted context omitted.

These terms are (or the lack of terms is) pretty horrible: Ubiquity, Argo, Spectrum, Accelerator. Sounds like names given to ironic sci-fi story characters.

If we are nitpicking, then I am compelled to point out that "ironic" doesn't mean what you may think it does: https://medium.com/@frithahookway/the-ironic-misuse-of-irony...

I think we could debate this.

> irony (ˈaɪənɪ) adj: of, resembling, or containing iron.

In all seriousness, if we want to get nitpicking let's go back to the fact that the word comes from the Greek eirōneia, which means feigned ignorance, which in turn comes from the Greek eirōn, dissembler. I'd then argue that naming things silly names can be called ironic if the story world feigns ignorance of them being silly.

Re: The fastest de-referer service... with AWS Global Accelerator

#39
post #38

Earlier quoted context omitted.

If we are nitpicking, then I am compelled to point out that "ironic" doesn't mean what you may think it does: https://medium.com/@frithahookway/the-ironic-misuse-of-irony...

I think we could debate this. > irony (ˈaɪənɪ) adj: of, resembling, or containing iron. In all seriousness, if we want to get nitpicking let's go back to the fact that the word comes from the Greek eirōneia, which means feigned ignorance, which in turn comes from the Greek eirōn, dissembler. I'd then argue that naming things silly names can be called ironic if the story world feigns ignorance of them being silly.

Point taken (:

> I think we could debate this.

Wouldn't be worth both our time though.

Re: The fastest de-referer service... with AWS Global Accelerator

#40
So I have found if you put your origin behind cloudfront and set it to not cache you can get similar if not better performance since you have low latency at the edge and the benefit of shared tcp connection for all assets with the origin… the last part means using http2 and serving up your assets on the same domain as the origin….
Post reply on HN