3 ms·

SSL termination is the most latency sensitive thing in the stack, I wasn’t talking about provisioning. With HTTP 2.0 you get to reuse the connection, so it’s no

by deno 9y ago

SSL termination is the most latency sensitive thing in the stack, I wasn’t talking about provisioning. With HTTP 2.0 you get to reuse the connection, so it’s not as critical. Anyway my point was you can get all those features without involving heavy L7 multitenant MITMaaS. I stand by it. > Which makes a lot of sense because if you are going use a proxying CDN Yes, but is proxying CDN the most optimal solution if you need those features. Isn’t that the relevant question.

laumars 9y ago
> SSL termination is the most latency sensitive thing in the stack That really depends on your infrastructure and how it copes with load. Latency can be introduced in so many different areas. While some parts of the stack might operate at a much lower latency, they can quickly cause far more significant bottlenecks once throughput is increased - even just marginally. This is why load testing is so important - it's easy to make generalised statements but it's even easier to overlook something or poorly tune one of the numerous ratios one defines in a typical complex stack. > Anyway my point was you can get all those features without involving heavy L7 multitenant MITMaaS. I stand by it. It's an irrelevant point because the discussion was never about whether it was possible or not to do the above. > Yes, but is proxying CDN the most optimal solution if you need those features. Isn’t that the relevant question. * It's cheaper than rolling your own solution, * It's quicker than rolling your own solution, * And it's easier to maintain than rolling your own solution. Plus, frankly, most companies don't have the infrastructure talent to build solutions that could compete with the uptimes, throughput and latency that they would get from Akamai, Cloudflare or AWS. So basically "yes"; in a great many cases a proxying CDN is the most optimal solution for the same reasons why writing backend web code in higher level languages is optimal than writing them in C or assembly.

by deno 9y ago

laumars 9y ago

> SSL termination is the most latency sensitive thing in the stack That really depends on your infrastructure and how it copes with load. Latency can be introduced in so many different areas. While some parts of the stack might operate at a much lower latency, they can quickly cause far more significant bottlenecks once throughput is increased - even just marginally. This is why load testing is so important - it's easy to make generalised statements but it's even easier to overlook something or poorly tune one of the numerous ratios one defines in a typical complex stack. > Anyway my point was you can get all those features without involving heavy L7 multitenant MITMaaS. I stand by it. It's an irrelevant point because the discussion was never about whether it was possible or not to do the above. > Yes, but is proxying CDN the most optimal solution if you need those features. Isn’t that the relevant question. * It's cheaper than rolling your own solution, * It's quicker than rolling your own solution, * And it's easier to maintain than rolling your own solution. Plus, frankly, most companies don't have the infrastructure talent to build solutions that could compete with the uptimes, throughput and latency that they would get from Akamai, Cloudflare or AWS. So basically "yes"; in a great many cases a proxying CDN is the most optimal solution for the same reasons why writing backend web code in higher level languages is optimal than writing them in C or assembly.