Roadmap

[StarpTech]

Hi @davidmarkclements @mcollina I think we should create a roadmap to work on the right things.
At the moment there are lots of ideas. We should focus on the minimum to make it operational.

I suggest

• Writing down the api interface

• Implement a logging interface

• Clear concept of error handling + implementation

• Implement an interface for payload validation

• Make HTTP/TCP Transports stable.

[davidmarkclements]

hey @StarpTech

Writing down the api interface

yep

Implement a logging interface

this is done - mu.log is a pino instance

Clear concept of error handling + implementation

yeah we're getting there

Implement an interface for payload validation

not sure this should be part of core, I'll answer this on the issue you answered

Make HTTP/TCP Transports stable.

tcp is approaching stability - although it'll need battletesting for sure, http still to do

[davidmarkclements]

let's use this issue as a bare bones roadmap for the moment

[tomdavidson]

What about a mesh transport similar to seneca mesh?

[davidmarkclements]

yah distributed transport is on the menu, potentially using https://www.npmjs.com/package/swim-hashring

[davidmarkclements]

it doesn't necessarily come under "minimum to make operational" though

[mcollina]

@davidmarkclements probably you'll just need https://github.com/mcollina/baseswim.

[davidmarkclements]

@mcollina yah thanks I realised that shortly after

[pelger]

@StarpTech PR in for HTTP transport - #74. Would welcome a review if you have bandwidth!

[pelger]

On SWIM, looking to implement discovery adapters most likely consul / etcd first, followed by a gossip based adapter. Agreed that we should pull together a more formal road map, will aim to pull one together for review soon!