Skip to content

Protocol

Sebastiaan Mannem edited this page May 14, 2016 · 1 revision

There is much thought about protocol's that can and should be used. The following should be possible:

  1. One implementation for alle communication between all microservices
  2. Management and control
    • Read and change configuration of the Koios cluster
    • Read status of components
    • Trigger data sync and rebalancing
  3. Data communication per record
  4. Data communication for total recordset (bulk)
  5. Security
    • Handshake channel security
    • Communication isolation
    • Authentication and authorization with low footprint
  6. Stateless layer 3, but statefull sessions with longer duration
There are three main thoughts about implementation:
  • REST/json
  • The SQLwire protocol of postgres
  • a custom protocol
First implementation will be aiming at REST and see from there what issues might arise. First issues are:
  • we need a good REST implementation for C (given that basic coding will be done in C).
  • REST is optimized for stateless, where koios might not be.
However, lets just start from there.

Clone this wiki locally