Disclaimer: I work on Compute Engine, not this (so I only sort of know what I'm talking about).
They're not trying to do those niche features (yet?). They're just trying to improve site perf for anyone using HTTP LB's on GCP already. You check a single box and your content is magically served from (or terminated on) a crazy number of POPs with zero configuration.
Having used both AWS and GCE, and I vastly prefer GCE. It is simply easier to use and offers better price/performance.
As to load balancing, I assume the poster is referring to the need to "pre-warm" ELB if you actually want to scale while our Maglev based load balancing goes from 0 to 1M qps within a minute.
Finally, EBS with provisioned IOPS is a good product! But so is PD-SSD, and you don't need to be a storage expert to get the best performance.
As others have pointed out, we've made a lot of progress in the last couple of years. Give us a closer look!
Disclosure: I work on Compute Engine.
"In certain scenarios, such as when flash traffic is expected, or in the case where a load test cannot be configured to gradually increase traffic, we recommend that you contact us to have your load balancer "pre-warmed". We will then configure the load balancer to have the appropriate level of capacity based on the traffic that you expect. We will need to know the start and end dates of your tests or expected flash traffic, the expected request rate per second and the total size of the typical request/response that you will be testing."
Edit: This means ELB could not deal with sudden spikes of traffic.
Disclosure: I work on Compute Engine.
Any reference for this claim?
Also, if people mostly cared about "the fastest", you'd see only Akamai in the past, but, no, people wanted freedom! I was stuck with Akamai and their $600/hr professional services for too long to know this first-hand! And "the fastest" is when the service is not heavily utilized like the rest and it has very limited functionality. Plus, other vendors constantly improve as well. The fastest service today is not the fastest of the tomorrow, but the one that starts with a minuscule subset of the baseline and what the others is doomed!
I think Microsoft is looking to capture their F500 base that are highly Windows/AD-centric.
Am I missing something?
Note that for YC, the number is $500k.
With Lambda, API Gateway, WAF, and ECS, DynamoDB or RDS, you pretty much can cover 95% of the usage scenarios.
[0]: https://www.varnish-cache.org/docs/4.1/reference/vcl.html
Council Bluffs, IA (us-central1) Berkeley County, SC (us-east1) St. Ghislain, Belgium (europe-west1) Changhua County, Taiwan (asia-east1)
So on any cache miss at one of the 50+ edge POPs, the cloud HTTP(S) load balancer will direct the request to the nearest cloud region. The resulting cache fill happens over Google's global network, which is fast. Once that cache fill happens, that edge cache can serve the content directly to clients, which is even faster.
Edit: Any chance you could ask Cedexis to add GCDN to these reports: http://www.cedexis.com/reports/#?report=dsa&country=US&date=...
I think the author of this blog post is trying to simplify the explanation (or just doesn't understand). No 'copy' of your site is running on the closest location. GCE is not available in all POPs.
These results would look very different if EC ADN was included. And not including CloudFlare is a bit strange.
Both EC and CF run Anycast CDNs. This is still a really cool thing for Google to release because it's nice to have more competition in the space.
I've run some prelim tests on pure route latency from 90+ worldwide locations and GC-CDN (? :) is pretty evenly matched with CF/EC.
The real test would be end to end HTTP request latency and this is where GC-CDN would probably beat out CF (since you're on the Google net from POP to GCE DC, which is nice and fast, whereas CF talks to your origin over the public Internet). EC ADN is symmetric (POP to POP is on-net) so probably more comparable.
I'm not seeing what's so special here. Other CDNs can do whole-site acceleration and caching (Akamai Sureroute, EdgeCast ADN).
> It is a whole new take in the concept of CDNs, going way further than simply caching files, since it is directly integrated into their Load Balancing system and it literally means that a copy of your site will be running and serving from the closest location to your customers, with a single public IP address thanks to Anycast.
This makes it sound like Google is magically making your GCE instances run in each of their POPs. What if those instances need to share state? What happens when a page does 10 SQL queries to a server halfway around the world?