I think github should allow me as a user to confirm contributions made out of the system, at least the first time per repo.
1,054 karma · joined November 21, 2014
I think github should allow me as a user to confirm contributions made out of the system, at least the first time per repo.
For anyone who wants to checkout a previous version of Kelsey's workshop, it can be found on youtube:
https://www.youtube.com/watch?v=tA8XNVPZM2w
https://www.youtube.com/watch?v=I9pF-Bv8AkI
https://www.youtube.com/watch?v=UZbwDH-_a_M
It's a very good introduction.
This is really exciting! There goes a theory. Charon seems to be also active, perhaps this suggests they split not so long ago? If that were the case it would be really interesting to know what hit them.
Nothing, your solution is obviously better than having none and it's enough for your needs. But the original discussion was about what's needed for DO to become a competitor for big business, not low budget, there they are already king.
Normally you want at least IP failover, meaning that you get an IP and can be rerouted to a different server with an simple API call. At work we use hetzner, which is not exactly a high-end provider but offers it: http://wiki.hetzner.de/index.php/Failover/en
Then, can be even better if the provider offers this HA-load balancer as a service, so you don't have to setup anything.
You might still need DNS failover to recover from a full datacenter going offline.
It's not a 30 second outage! Your domain will keep resolving the bad IP. Even with an extremely low TTL (also not recomendable) ISP's DNS will cache it and even some will ignore your TTL. A big portion of all new users will keep hitting the bad IP.
Anyway, I won't try to convince you to change your setup if you are happy with it, but it's obvious from the comments that I'm not the only one thinking it's a suboptimal solution, so at least some of us won't be considering DO for HA systems given the circumstances.
> if no response in ~30 seconds, try the second
That is not HA. Most people will not wait 30 seconds for a page to load. If your business looses money with every minute of downtime this is certainly not adequate. It's certainly not recommended https://en.wikipedia.org/wiki/Round-robin_DNS#Drawbacks
> On average the programs in the Go 1 benchmark suite run a few percent faster in Go 1.5 than they did in Go 1.4, while as mentioned above the garbage collector's pauses are dramatically shorter, and almost always under 10 milliseconds.
And I guess 2015 will be too, I just can't wait :)
How? How does the DNS client know that the IP no longer works? do browsers today have this mechanism?
I'm not a network guy so perhaps I'm wrong but it's my understanding the problem with DNS load balancing is that you can not invalidate the TTL on the client.
It seems to me like they've included Google's trace viewer[0] into the go tool, nice.
Great to hear. Real private networking, object/shared storage and most importantly HA (IP failover/load balancing) is all DO is missing to start really competing with AWS for "big business".
That right there might be the root of all EU problems.
Just noticed how they are not linking Docker, I guess there are still some frictions :)