3 ms·

I'm one of the Core authors of the Kite library (library for writing micro services). I wrote an extensive introduction here on GopherAcademy: http://blog.gophe

by farslan 12y ago

I'm one of the Core authors of the Kite library (library for writing micro services). I wrote an extensive introduction here on GopherAcademy: http://blog.gopheracademy.com/birthday-bash-2014/kite-microservice-library/ http://blog.gopheracademy.com/birthday-bash-2014/kite-micros... I think Gotalk and Kite have a lot of common (for example we have also kite.js, to talk with browsers). The mission of the Kite library is the same as with Gotalk, mainly to communicate two pieces of software in an easy way. However in order to achieve this Kite also has an inbuilt service discovery mechanism. I think this is really important because with time you are app number will increase and service discovery is a must have. There are many differences too, for example protocol (we use JSON). Congrats on shipping this, I'm really looking forward to see how it evolves and how you solve upcoming problems (such as poor network conditions where Websocket badly fails).

zimbatm 12y ago
Wouldn't it be more fair to compare Gotalk to Kite's underlying dnode-protocol[1] ? Personally Gotalk's protocol seems much better thought out; size-prefixed messaging, rpc & streaming support, multiplexing (especially important with WebSocket). The only missing bit would be some form of heart-beating. * [1] https://github.com/substack/dnode-protocol https://github.com/substack/dnode-protocol
- jra_samba 12y ago
  Messages need to be encrypted by default. No more cleartext protocols on the network anymore please, for obvious reasons.
  - rasmusfabbe 12y ago
    With Gotalk, you can use the byte-buffer request and response functionality (instead of the JSON-encoding versions) and e.g. dec.XORKeyStream(inbuf, payload) in your handler when receiving a payload followed by enc.XORKeyStream(payload, outbuf) when responding.
    - irq-1 12y ago
      You could add symmetric encryption before and after putting anything on the network, and let users turn it on with a simple setting. Here's the fun part: you could use go generators to create a local key when the package is compiled. Then you wouldn't need to embed a key, or ask the user to generate and pass in a key.
rasmusfabbe 12y ago
Hello Farslan, I'm the author of Gotalk and just read your article on Kite — very interesting! In the scenario of composing distributing systems where you'd e.g. want to "map-reduce this data on some number of cores" service discovery is important. However I wrote Gotalk to be as small as possible, meaning I hope it can become one of those small packages I feel comfortable using in any of my projects. The "small" part here is key: that it feels small. Perhaps there's an approach where a completely decoupled service-discovery package exists which can be combined with Kite or Gotalk to form auto-discovering clusters of programs. Thanks for bringing Kite to our attention.

by farslan 12y ago

zimbatm 12y ago

Wouldn't it be more fair to compare Gotalk to Kite's underlying dnode-protocol[1] ? Personally Gotalk's protocol seems much better thought out; size-prefixed messaging, rpc & streaming support, multiplexing (especially important with WebSocket). The only missing bit would be some form of heart-beating. * [1] https://github.com/substack/dnode-protocol https://github.com/substack/dnode-protocol

jra_samba 12y ago
Messages need to be encrypted by default. No more cleartext protocols on the network anymore please, for obvious reasons.
- rasmusfabbe 12y ago
  With Gotalk, you can use the byte-buffer request and response functionality (instead of the JSON-encoding versions) and e.g. dec.XORKeyStream(inbuf, payload) in your handler when receiving a payload followed by enc.XORKeyStream(payload, outbuf) when responding.
  - irq-1 12y ago
    You could add symmetric encryption before and after putting anything on the network, and let users turn it on with a simple setting. Here's the fun part: you could use go generators to create a local key when the package is compiled. Then you wouldn't need to embed a key, or ask the user to generate and pass in a key.

rasmusfabbe 12y ago

Hello Farslan, I'm the author of Gotalk and just read your article on Kite — very interesting! In the scenario of composing distributing systems where you'd e.g. want to "map-reduce this data on some number of cores" service discovery is important. However I wrote Gotalk to be as small as possible, meaning I hope it can become one of those small packages I feel comfortable using in any of my projects. The "small" part here is key: that it feels small. Perhaps there's an approach where a completely decoupled service-discovery package exists which can be combined with Kite or Gotalk to form auto-discovering clusters of programs. Thanks for bringing Kite to our attention.