API will use JAX-RS to keep a command oriented API which matches what we want to do and is aligned on Talend knowledge and team capability to fix the stack, now we must decide if we use http or websocket (or something else) protocol. Websocket seems way more accurate for the usage we do (machine to machine) but we need to study it.

Some inputs:

• K-Engine will need a communication direction control, it can use proxies but it can not be needed technically too (conversation in progress, ensure to have the info when working on that task)
• WebSocket being a connected protocol we'll be faster than HTTP and it is not an issue cause clients will not be volatile in our infra