Sha256: d9fecba6067e3ea4b19fffa259f641bba3c3a4a11b7453e82618fed9f369c253
Contents?: true
Size: 1.31 KB
Versions: 51
Compression:
Stored size: 1.31 KB
Contents
Feature: request balancer error handling
In order to enhance app availability and development velocity
RequestBalancer should consider certain errors as fatal by default
So careless developers do not cause unexpected behavior when failures occur
Scenario: well-behaved servers
Given 5 servers that respond with 200
When a client makes a load-balanced request to '/'
Then the request should complete
And the request should be attempted once
Scenario: resource not found
Given 4 servers that respond with 404
When a client makes a load-balanced request to '/'
Then the request should raise ResourceNotFound
And the request should be attempted once
Scenario: client-side error
Given a server that responds with 200
When a client makes a buggy load-balanced request to '/'
Then the request should raise ArgumentError
And the request should be attempted once
Scenario: socket open timeout
Given 2 blackholed servers
When a client makes a load-balanced request to '/'
Then the request should be attempted 2 times
And the request should raise NoResult
Scenario: HTTP request timeout
Given 2 overloaded servers
When a client makes a load-balanced request to '/'
Then the request should be attempted 2 times
And the request should raise NoResult
Version data entries
51 entries across 51 versions & 1 rubygems