4 ms·
A CDN might be fine for public, static content, or certain kinds of APIs, but a CDN does nothing for most "transactional" APIs. If you are trying to host a mul
by numbsafari 10y ago
A CDN might be fine for public, static content, or certain kinds of APIs, but a CDN does nothing for most "transactional" APIs.
If you are trying to host a multi-region deployed API, and your customers are evaluating your infrastructure against NIST and other security guidelines and recommendations, a TLS proxy is considered a security problem (go back a few months to CloudFlare's massive data exposure). You want your TLS terminated directly at your own service hosts.
In that situation you want an SNI aware LB that simply does host-based routing. You cannot achieve this today with GCPs HTTP(s) LB. Which is a pain, because it's otherwise awesome sauce.