Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Datapath.io: Provider-Independent Elastic IP Addresses

datapath.io

Post reply on HN
Print view View original

11–20 of 24 posts

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#11

Post by rev_bird »

> What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses.

Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record pointing as Azure or Google Cloud or your mom's laptop, whatever, and it'll do what Datapath is doing without futzing with your routing. ...right?

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#13

Post by hhw »

Doesn't every CDN already accomplish the same functionality with multiple origins and failover detection, while accelerating static content by caching it at the edge? Given how cost competitive CDNs already are, I don't see how they can charge a low enough cost in comparison to be compelling, while still incurring bandwidth costs and at least some network infrastructure which make it almost as expensive to run, minus some caching nodes. And if for whatever reason, there does happen to be some use case for anycasting the IP that's advantageous, any CDN could add this feature overnight while having a much more established footprint and infrastructure in place.

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#14

Post by amenonsen »

moe wrote: post #12

I'd suggest you scrap your "fancy" website and replace it with two paragraphs of text that explain what you are trying to sell and how it works. The "vague bullshit in between cute animations" approach really doesn't work at all for this type of product.

When I first saw the page (opened along with a bunch of other tabs from HN links), with its "Timeout error!" balloon and "Service disruption" headline, I thought it was a fancy error page and hit reload. Oops.

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#16

Post by sspies »

api wrote: post #4
wmf wrote: post #3

Do you have to pay for your traffic twice?

... and does this add hops?

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

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#17

Post by sspies »

rev_bird wrote: post #11

> What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses. Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record point…

You cannot do graceful failovers with Route 53. This is, because DNS is a system of many dependend caching layers and the TTL value is not realiable.

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#18

Post by moe »

sspies wrote: post #17
rev_bird wrote: post #11

> What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses. Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record point…

You cannot do graceful failovers with Route 53. This is, because DNS is a system of many dependend caching layers and the TTL value is not realiable.

the TTL value is not realiable.

How is the TTL not reliable?

In my personal experience DNS cut-overs have never been a problem. Is there any major OS or ISP doing DNS wrong?

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#19

Post by [deleted] »

sspies wrote: post #17
rev_bird wrote: post #11

> What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses. Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record point…

You cannot do graceful failovers with Route 53. This is, because DNS is a system of many dependend caching layers and the TTL value is not realiable.

[deleted]

Re: Datapath.io: Provider-Independent Elastic IP Addresses

#20

Post by sspies »

moe wrote: post #18
sspies wrote: post #17

Earlier quoted context omitted.

You cannot do graceful failovers with Route 53. This is, because DNS is a system of many dependend caching layers and the TTL value is not realiable.

the TTL value is not realiable. How is the TTL not reliable? In my personal experience DNS cut-overs have never been a problem. Is there any major OS or ISP doing DNS wrong?

We have seen providers set the TTL value to 300 seconds no matter what. Chrome has been caching names forever while running...just two examples
Post reply on HN