Re: Export Go - for preview
Dell - Internal Use - Confidentialtoggle quoted messageShow quoted text
Thanks for this Trevor and Drasko,
My top 3 requirements would be:
-Broker-less (we've done MQTT and broker before. It's not a problem, but additional broker requires more setup/containers/etc. and can be large footprint depending on implementation. We can and should still allow MQTT as alternative option for those that want it - like we have been offering in Java side to date - but the default should be brokerless).
-Go native (but also provides libraries for Java, C and possibly other languages). As we look at messaging use between other services in the future, support for polyglot is integral to our tenets and needs of the future.
-Lightweight, ease of use, etc.
What I am seeing on this thread is that people feel Nanomsg may be leading candidate?? Would like to hear from others that have an opinions or questions. I'd like to hold this as a major part of our discussion in the Go project meeting (once we have the mono repo work done).
From: Drasko DRASKOVIC [mailto:drasko@...]
Sent: Friday, February 23, 2018 10:23 AM
To: Conn, Trevor <Trevor_Conn@...>
Cc: White2, James <James_White2@...>; espy <espy@...>; Fede <fclaramonte@...>; dejan.mjc <dejan@...>; edgex-golang@...; manuel@...; Garcia, Gorka <Gorka.Garcia@...>
Subject: Re: [Edgex-golang] Export Go - for preview
On Fri, Feb 23, 2018 at 5:15 PM, <Trevor.Conn@...> wrote:
Dell - Internal Use - ConfidentialAgreed for Nanomsg, this is a good candidate (btw, I have mentioned this 6 months ago :)).
Simplicity. Whole system will be highly simplified, IMHO
Async bi-directional event sending. Protobuf included. Real TLS (because we have HTTP).
Mainflux Author and Technical Advisor
www.mainflux.com | Industrial IoT Cloud
Engineering Division | Paris, France