Warning: This library is under active development, and should not be considered production ready
The Graft project explores what the web could become, if we extended microservice architectures into the client.
When you graft something, it involves joining together parts to create a new whole. One that is hopefully more adaptable, resilient and ultimately interesting.
"Instead of pretending everything is a local function even over the network ..., what if we did it the other way around? Pretend your components are communicating over a network even when they aren't?" -- Docker's Solomon Hykes on LibChan - [link]
The main object of this library. A
Graft instance is a
The objects on the output of a
Graft instance are
Requests. On the input side, you can write just normal JS
objects, and everything else you can write to a jsChan
These objects will be automatically wrapped up in a Request.
Graft instance is backed by
In order to process the requests, you can just:
var graft = ;var through = ;graft;graft;
Returns a nested read channel, this channel will wait for data from the other party.
Returns a nested write channel, this channel will buffer data up until is received by the other party.
Passes the request to the first argument, and if that returns a truthy
value, it calls
write(req) on the associated stream.
It respect backpressure.
Shortcut for the most common usage of
graft.branch(), it allows to
Each Graft request is the first message sent on a top-level channel, and it is composed of:
_channel, the associated channel
_session, the associated session
Each request will have its own channel, but the session is generic for every client.
_session properties will not be enumerable.
Creates a new spdy client to pipe to:
var graft = ;var spdy = ;graft;graft;
Creates a new spdy server that you can pipe to a graft instance:
var graft = ;var spdy = ;var through = ;spdy;
Creates a new ws client to pipe to:
var graft = ;var ws = ;graft;graft;
Creates a new ws server that you can pipe to a graft instance:
var graft = ;var ws = ;var through = ;ws;
You can even pass an existing http server that will be hooked up, like so:
var graft = ;var ws = ;var http = ;var server = http;ws
Libchan is the connective tissue to all our endeavours. It is a microservices library announced by the Docker project, and it is going to form the basis of all of the tools they build in the future.
It's most unique characteristic is that it replicates the semantics of go channels across network connections, while allowing for nested channels to be transferred in messages. This would let you to do things like attach a reference to a remote file on an HTTP response, that could be opened on the remote end for reading or writing.
The protocol uses SPDY as it's default transport with MSGPACK as it's default serialization format. Both are able to be switched out, with http1+websockets and protobuf fallbacks planned.
While the RequestResponse pattern is the primary focus, Asynchronous Message Passing is still possible, due to the low level nature of the protocol.