CloudFlare Is Now a Google Cloud Platform Technology Partner • Hacker News Board

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#11

Post by zuck9 » Mon, Apr 13, 2015, 3:54 PM UTC

humanarity wrote: post #8

CloudFlare hosts reddit, is that correct?

Yes. The NS records list reddit nameservers (usually you need to use CF nameservers for using their service, using your own nameservers require more config) but the A records list CF IPs (free users just get two IPs, reddit has quite a lot)

    reddit.com.		22	IN	A	198.41.209.143
    reddit.com.		22	IN	A	198.41.208.141
    reddit.com.		22	IN	A	198.41.209.137
    reddit.com.		22	IN	A	198.41.208.139
    reddit.com.		22	IN	A	198.41.208.143
    reddit.com.		22	IN	A	198.41.208.142
    reddit.com.		22	IN	A	198.41.209.139
    reddit.com.		22	IN	A	198.41.209.141
    reddit.com.		22	IN	A	198.41.209.138
    reddit.com.		22	IN	A	198.41.209.140
    reddit.com.		22	IN	A	198.41.208.138
    reddit.com.		22	IN	A	198.41.208.137
    reddit.com.		22	IN	A	198.41.209.142
    reddit.com.		22	IN	A	198.41.208.140
    reddit.com.		22	IN	A	198.41.209.136

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#12

Post by andygambles » Mon, Apr 13, 2015, 3:58 PM UTC

So is this basically GCP and Cloudflare peering with each other?

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#13

Post by yla92 » Mon, Apr 13, 2015, 3:58 PM UTC

henningschuster wrote: post #5

Didn't Google announce their own DDOS protection service some month ago?

You mean the Project Shield[1] ?

[1]: https://projectshield.withgoogle.com/en/

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#14

Post by oaktowner » Mon, Apr 13, 2015, 4:17 PM UTC

nezo wrote: post #6

Is it going to be beta or alpha, like most Google Cloud services?

Google Product Manager here.

Not sure why you think most Google Cloud Services are in beta.

The Google Cloud products page [1] lists 17 main products. Two are in alpha (Container Engine, Deployment Manager), one is in beta (Pub/Sub).

The rest are fully supported. There are some beta features here and there...but saying "most" are in beta is certainly not correct.

[1] https://cloud.google.com/products/

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#15

Post by bingobob » Mon, Apr 13, 2015, 4:26 PM UTC

TeeWEE wrote: post #7

Wait, isnt google appengine already using SPDY?

HTTP/2 is replacing SPDY http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-ht...

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#16

Post by ddorian43 » Mon, Apr 13, 2015, 4:28 PM UTC

oaktowner wrote: post #14

nezo wrote: post #6

Is it going to be beta or alpha, like most Google Cloud services?

Google Product Manager here. Not sure why you think most Google Cloud Services are in beta. The Google Cloud products page [1] lists 17 main products. Two are in alpha (Container Engine, Deployment Manager), one is in beta (Pub/Sub). The rest are fully supported. There are some beta features here and there...but saying "most" are in beta is certainly not correct. [1] https://cloud.google.com/products/

Example: Data Flow is in Alpha & Logging is in Beta.

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#17

Post by josephmx » Mon, Apr 13, 2015, 4:30 PM UTC

abritishguy wrote: post #4

"double web content transfer times" That should be speeds.

Maybe they're gonna be twice as slow now?

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#18

Post by throwaway000002 » Mon, Apr 13, 2015, 4:30 PM UTC

This is sorta an internet architecture question for those in the know. Assuming there's no issue with client reachability/latency, what's stopping CloudFlare from having a single IP?

Suppose the IP was behind a fat enough pipe, why not load balance behind it instead of DNS load-balancing in front of it (and additionally behind each as I presume now happens)? Also, if that IP was anycast then you could ignore the issue of client latency as well, assuming you have the necessary private network behind endpoints to manage state.

If you don't like/can't solve the problem at the level of IP anycast, when not leverage a third-party anycast DNS and just have a few fixed IP for specific geographic locales, again with fat enough pipes and load balancing behind them.

I guess what I'm saying is that there's no reason for an organization, a monolithic entity, to have more that a handful IP addresses at most.

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#19

Post by nulltype » Mon, Apr 13, 2015, 4:31 PM UTC

ddorian43 wrote: post #16

oaktowner wrote: post #14

Earlier quoted context omitted.

Google Product Manager here. Not sure why you think most Google Cloud Services are in beta. The Google Cloud products page [1] lists 17 main products. Two are in alpha (Container Engine, Deployment Manager), one is in beta (Pub/Sub). The rest are fully supported. There are some beta features here and there...but saying "most" are in beta is certainly not correct. [1] https://cloud.google.com/products/

Example: Data Flow is in Alpha & Logging is in Beta.

Go on App Engine has been in beta for years

Re: CloudFlare Is Now a Google Cloud Platform Technology Partner

#20

Post by jgrahamc » Mon, Apr 13, 2015, 4:33 PM UTC

throwaway000002 wrote: post #18

This is sorta an internet architecture question for those in the know. Assuming there's no issue with client reachability/latency, what's stopping CloudFlare from having a single IP? Suppose the IP was behind a fat enough pipe, why not load balance behind it instead of DNS load-balancing in front of it (and additionally behind each as I presume now happens)? Also, if that IP was anycast then you could ignore the issu…

1. Non-SNI based SSL means you need an IP per host.

2. People attack IP addresses. Handy to be able to change the IP address of a web site.

3. Countries block sites based on IP addresses. Handy to be able to move sites around to prevent collateral damage.