News for hackers. Stuff that matters.

A comment on Datapath.io: Provider-Independent Elastic IP Addresses. Parent comment

Re:Datapath.io: Provider-Independent Elastic IP Addresses by api on Wednesday January 28, 2015 @07:49PM (#8963655)
... and does this add hops?
[ Parent | on HN ]
Re:Datapath.io: Provider-Independent Elastic IP Addresses by sspies on Thursday January 29, 2015 @02:54AM (#8964867)
Id adds one hop (our appliance) to the path. It tries to increase performance of your path by taking non-standard BGP metrics into account: congestion and latency
[ Parent | on HN ]
Re:Datapath.io: Provider-Independent Elastic IP Addresses by moe on Thursday January 29, 2015 @03:11AM (#8964918)
Does that mean all traffic passes through your appliance?

Where is it physically located, what about congestion of the appliance itself, what are your peerings?

[ Parent | on HN ]
Re:Datapath.io: Provider-Independent Elastic IP Addresses by sspies on Thursday January 29, 2015 @03:18AM (#8964932)
Traffic passes the appliance at the edge of the hosting provider. It takes congestion at all links and the appliance itself into account and re-routes accordingly. Depending on the characteristics of the location, at least three very unsimilar transit connections are used.
[ Parent | on HN ]
Re:Datapath.io: Provider-Independent Elastic IP Addresses by moe on Thursday January 29, 2015 @03:27AM (#8964956)
at least three very unsimilar transit connections are used.

What does transit mean in this context; like between my VPC and your appliance? Can you give an example for e.g. an AWS region?

How is the appliance implemented, is it physical hardware, EC2 instances? Is it redundant, how do you scale it in terms of bandwidth?

[ Parent | on HN ]
Re:Datapath.io: Provider-Independent Elastic IP Addresses by sspies on Thursday January 29, 2015 @03:41AM (#8964997)
Transit providers sell access to the whole internet to us. We are in negotitations with them, but we will be more specific, once we have the commitments. Technically, we choose at least three different providers, so our appliance has a good basis of decision-making. For the connection between your VPC and our appliance, we use the regular AWS DC API.
[ Parent | on HN ]