Service discovery aware rest client with client side load balancing.
Service discovery aware declarative rest client with client side load balancing.
Sarathi is a rest client for microservices. It is modelled similar to probably the most popular rest client of this sort in Java world: Feign (spring-cloud-feign) and its load balancer: Ribbon (spring-cloud-ribbon), both from Netflix and fall under spring cloud project.
npm install --save sarathi
var SarathiClientBuilder = require("sarathi");
var testServiceClient = new SarathiClientBuilder().setConfig(options).build();
var SarathiClientBuilder = require("sarathi");
var clientBuilder = new SarathiClientBuilder();
var client = clientBuilder.setConfig({
restClient: {
retry: 2
},
loadBalancer: {
strategy: "round-robin"
}
})
.setDiscoveryStrategy(new ConsulDiscoveryStrategy({serviceId: "express-service"}))
.addMethod("getUsers", "/users")
.addMethod("getUser", { url: "/users/{id}", headers: {accept: "text/html" }})
.build();
client.getUsers(function(error, response, body) {
console.log(body);
});
client.getUsers().then(function(responseObject) {
console.log(responseObject.response); // Entire http response object
console.log(responseObject.body);
}, function(err) {
console.log(err);
})
client.getUser({placeholders: { id: 4 }, headers: {someHeader: "value"}}, function(error, response, body) {
console.log(body);
});
client.getUsers({queryParams: {name: "nikhil"}}, function(error, response, body) {
console.log(body);
});
client.getUsers({httpMethod: "POST", body: {v: "some body"}}, function(error, response, body) {
console.log(body);
});
client.getUsers({httpMethod: "POST", body: '{"v": "some body"}' }, function(error, response, body) {
console.log(body);
});
Please return when you are sober ;)
NOTE: API is much more fun
Object
declaring method name, endpoint they refer to, http method etc.Object
Load balancer configurationObject
Instance of service discovery strategyObject
Rest client configurationObject of method description objects. Key of the object is your method name: Ex: getUsers and value as describe below. Apart from parameters mentioned below any additional parameters supported by the request client should also work (not all tested) as Sarathi transparently forwards them to request module internally.
String
Corresponding http endpoint, can have placeholders. Ex: /users OR /users/{id}String
HTTP method, Ex: “GET”Object
a map of values to resolve placeholders, should ideally be passed while invoking the method instead. Ex: {id: 1}Object
all attributes of this object are passed as query parameters. Ex: {a: 1, b: 2} becomes: ?a=1&b=2Object
any headers you might want to set. By default: {“content-type”: “application/json”, “accept”: “application/json”} are always set, which can be overridden. String|Object
for POST/PUT requests.String
Possible values, Ex: “round-robin”Object
Instance of sarathi-discovery-strategy, currently available implementations: nodiscovery (when no discovery server), consul.ionumber
Number of times to retry when error occurs in a REST call. If load balancing is enabled, the load balancing strategy decides where the next call will go to. Total calls triggered in worst case will be 1 + retry.number
in ms. Timeout for rest calls.
{
methods: {},
loadBalancer: {
strategy: "round-robin"
},
discoveryStrategy: undefined,
restClient: {
retry: 2,
timeout: 2000
}
}
{
"url": undefined,
"method": "GET",
"placeholders": {},
"qs": {}, //query params
"headers": {
"content-type": "application/json",
"accept": "application/json"
},
"body": undefined
}
{
methods: { // methods to define on this client and their endpoints and other parameters
getUsers: "/users",
getUser: { url: "/users/{id}", "accept": "application/xml"}
},
loadBalancer: { // Load balancer config
strategy: "round-robin" // random, disabled
},
discoveryStrategy: new ConsulDiscoveryStrategy({serviceId: "user-service"}),
restClient: { // Rest client config
retry: 2, // number of retries on failure before returning error; value 2 means: 1 + 2 = 3 max calls.
timeout: 2000 // REST call timeout
}
}
A fluent API for setting all configurations
constructor, sets the options as passed. Options not mandatory.
override anything set in constructor.
adds a single method to the client, with provided method options. If you are fine with defaults, just pass the url instead.
set all methods on client, with structure as {methodName: methodOptions, methodName2: methodOptions2}
set config for rest client.
:Number
)set the retry count for rest client.
:String
)set the strategy for load balancing
Object
)Instance of sarathi-discovery-strategy, currently available implementations: nodiscovery (when no discovery server), consul.io
returns an object with default values of methodOptions
builds the configuration provided and returns the restClient.
Methods added on the client return promises which can be used instead of passing callback to the method.
Coming soon. Its here!! Now that methods return promise, just use as described in hystrixjs documentation.
var CommandsFactory = require('hystrixjs').commandFactory;
var serviceCommand = CommandsFactory.getOrCreate("Service on port :" + service.port + ":" + port)
.circuitBreakerErrorThresholdPercentage(service.errorThreshold)
.timeout(service.timeout)
.run(client.getUsers) // This is where the call is
.circuitBreakerRequestVolumeThreshold(service.concurrency)
.circuitBreakerSleepWindowInMilliseconds(service.timeout)
.statisticalWindowLength(10000)
.statisticalWindowNumberOfBuckets(10)
.errorHandler(isErrorHandler)
.build();
serviceCommand.execute(); // Trigger the API
...
.run(function(options) {
return client.getUser(options);
})
...
serviceCommand.execute({placeholders: {id: 1}, headers: {"content-type": "application/xml"}});
Pronounce it as /sa:raθiː/, it is a noun. It simply means: a charioteer. A sarathi controls the chariot, chooses the best route and navigates it. According to Hindu mythology, it also is an epithet of Krishna, an Avatar of Vishnu, who played the role of Arjun’s charioteer, in the great war of Mahabharata and led him to victory.