4 ms·
All great ideas. Another suggestion: Terminate somewhere else. If you fit inside of the CloudFlare T&Cs, you can probably save a much larger amount terminati
by alex_young 7y ago
All great ideas.
Another suggestion:
Terminate somewhere else.
If you fit inside of the CloudFlare T&Cs, you can probably save a much larger amount terminating there and having them peer with you using the same TLS every time, or failing that, try someone like BunnyCDN.
I've found that while AWS CloudFront is easy to instrument, it's neither very performant (lots of cache misses even when well configured), or cost effective (very high per byte cost).
- stefan_ 7y agoThis. If your service is collecting aggregated analytics data from users, bytes that those users would never care to send in the first place, you can get vastly vastly better pricing on traffic by going with providers that don't care too much about high-quality peering.
- StavrosK 7y ago> terminating there and having them peer with you using the same TLS every time Can you elaborate for someone who isn't that familiar with networking? How does this work?
- Taik 7y agoThis is basically saying, use a 3rd party CDN (e.g. Cloudflare) to handle and terminate client connections, letting the CDN pipeline the actual requests through a handful of persistent connections to your server.
- StavrosK 7y agoAh, I see, thank you. So this is just to avoid TLS negotiation every time.
- deleted 7y ago[deleted]