3 ms·
CAP is not applicable here from what I can tell. Glad to know Coda Hale understands it though. Sounds like a real nice guy.
by askimto 14y ago
CAP is not applicable here from what I can tell. Glad to know Coda Hale understands it though. Sounds like a real nice guy.
- semisight 14y agoForgive my ignorance, but why isn't CAP applicable here?
- eitland 14y agoWhile I didn't state thate it is CAP isn't applicable one interesting point is that CAP concerns itself with distributed computer systems. While I guess almost all systems built on top of heroku almost by definition needs to be distributed in some way heroku itself doesn't need to be. (Not saying it isn't.)
- aphyr 14y agoheroku itself doesn't need to be [distributed]. Yes, it does.
- askimto 14y agohttp://en.wikipedia.org/wiki/CAP_theorem http://en.wikipedia.org/wiki/CAP_theorem How does consistency apply here for example?
- aphyr 14y agoConsistency applies because a least-conns load balancer requires state: it needs to know how many connections are open for each node. A distributed least-conns load balancer requires distributed state. This is problematic because the convergence times for state like "connection counts" between load balancers in different datacenters could be significantly higher than the rate at which that state itself is changing, and the cost to getting that state wrong is significantly higher latencies. That's where you start having to make CAP and latency tradeoffs.
- askimto 14y agoWell, sure. Does that make stateless load balancers consistent, though? :) I just don't think the CAP terminology helps.
- codahale 14y agoJust call me an asshole already and have done with it.