[zeromq-dev] Q: distributed configuration access - recommendations?

[Pieter Hintjens]

If you're going to use ZeroMQ anyhow, look at the Clone pattern from
the Guide. This is a distributed configuration management system. It
does depend on a central server in its current design, to ensure
ordering. You could simplify that, if you don't care about ordering
(i.e. updates on same key).

On Sun, Feb 16, 2014 at 11:35 AM, Michael Haberler <mail17 at mah.priv.at> wrote:
> I'm retroftting zeroMQ into what used to be an all-on-one-host application; it goes distributed, and some parts are on embedded systems. Still another part would be UI's which could be Gtk, Qt, Java, or JS/websockets.
>
> I'm looking for a robust method for distributed configuration data access.
>
> Currently .ini files are used for configuration access - downstream managing .ini files on several hosts will be a pain, and I'm lukewarm about distributed file system access.
>
> .ini files are what folks understand and are happy with, but its not a knockout requirement.
>
> A zeromq-based solution would be OK, autodiscovery beacon-style is already in place.
>
> Any recommendations?
>
> I was thinking of redis as one option, but that'd be just a keystore machine, and possibly a bit heavy-handed for the purpose.
> I looked at coyaml, which is great for single-host; but requires Python3 and lacks a distributed access layer.
>
> - Michael
>
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev