Live data from Hacker News

Introducing Network Service Tiers

cloudplatform.googleblog.com

1–10 of 215 posts

Re: Introducing Network Service Tiers

#2
> There are at least three independent paths (N+2 redundancy) between any two locations on the Google network, helping ensure that traffic continues to flow between these two locations even in the event of a disruption. As a result, with Premium Tier, your traffic is unaffected by a single fiber cut. In many situations, traffic can flow to and from your application without interruption even with two simultaneous fiber cuts.

What does this mean? N+2 redundancy should mean, that even if both go down, then service will not be affected at all, no?

Re: Introducing Network Service Tiers

#5
post #2

> There are at least three independent paths (N+2 redundancy) between any two locations on the Google network, helping ensure that traffic continues to flow between these two locations even in the event of a disruption. As a result, with Premium Tier, your traffic is unaffected by a single fiber cut. In many situations, traffic can flow to and from your application without interruption even with two simultaneous fibe…

N+2 usually means one redundancy for normal operations (deploys, maintenance) and one for disruptions. If the disruption happens while there is an ongoing maintenance, you'll be resilient for one event only.

Re: Introducing Network Service Tiers

#6
post #2

> There are at least three independent paths (N+2 redundancy) between any two locations on the Google network, helping ensure that traffic continues to flow between these two locations even in the event of a disruption. As a result, with Premium Tier, your traffic is unaffected by a single fiber cut. In many situations, traffic can flow to and from your application without interruption even with two simultaneous fibe…

Two fiber cuts in a N+2 network could overload the last remaining path, resulting in some impact on service.

Re: Introducing Network Service Tiers

#7
I thought I read an article about an online game company who was doing something similar with their users; trying to get their users on their private network as soon as possible. Does anyone else remember that article on HN?

Re: Introducing Network Service Tiers

#8
post #6
post #2

> There are at least three independent paths (N+2 redundancy) between any two locations on the Google network, helping ensure that traffic continues to flow between these two locations even in the event of a disruption. As a result, with Premium Tier, your traffic is unaffected by a single fiber cut. In many situations, traffic can flow to and from your application without interruption even with two simultaneous fibe…

Two fiber cuts in a N+2 network could overload the last remaining path, resulting in some impact on service.

I think this would (or should) be called N+1.

Edit: but you're right, this might be what they mean.

Re: Introducing Network Service Tiers

#9
Reading this I just got stumped by how many stacks, layers, hardware, technologies, and knowledge incorporated into all of that those bytes needed to travel so I could read them on a laptop across the globe

Re: Introducing Network Service Tiers

#10
So is this like the app engine price hike debacle a few years ago but with "better" messaging? So "Try Network Service Tiers Today" means "Migrate to Standard Tier today to avoid the massive price increases coming soon"?

But fundamentally they just massively underestimated costs and need to find a way to adjust pricing. With app engine it was very conveniently beta, so they used the end of beta for the price hike. For this, they're having to invent a "Premium" and a "Standard" Tier, and hey guess what, everyone has been using "Premium".

My experience so far with Google has been "Use this now, and we'll have a massive price hike later, if we keep it around at all."

Post reply on HN