blackcat786

7 ms·

1.
by blackcat786 16y ago
The need for HA software to remap ip's should not be there if the service has been designed in a stateless manner. As soon as a service goes down the balancer should send the next request to the next node. In addition - At the entrance of
2.
Cloudonomics: High Availability should be a part of your cloud computing ROI(ringio.com)
11 points by blackcat786 16y ago|6 comments
3.
High Availability Principle : Request Queueing(saasinterrupted.com)
22 points by blackcat786 17y ago|0 comments
4.
by blackcat786 17y ago
Exactly. There is always a "deployed system limit" even in horizontally scaling DB layers as deployed with sharding etc.
5.
by blackcat786 17y ago
The challenge is that by the time you reach the 300th request your system is unusable. In the example mentioned the system starts to experience exponential degradation around the 100th request. One wants to avoid reaching that state of th
6.
High Availability Principle : Concurrency Control(saasinterrupted.com)
11 points by blackcat786 17y ago|6 comments
7.
The organizational impact due to poor software quality(saasinterrupted.com)
19 points by blackcat786 17y ago|1 comments
8.
How fault tolerant is your team?(saasinterrupted.com)
2 points by blackcat786 17y ago|0 comments
9.
The Most Common Flaw In Software Performance Testing(saasinterrupted.com)
18 points by blackcat786 17y ago|2 comments
10.
How not to interview people(saasinterrupted.com)
4 points by blackcat786 17y ago|0 comments
11.
High uptime equates to low mean time to recovery(saasinterrupted.com)
24 points by blackcat786 17y ago|1 comments