FWIW I have come to believe that trying to design or even understand the overall flows of data is a mistake, at least when you want to scale.
What does scale is to speak of protocols and implementations. I know this isn't a happy answer yet it's a proven one (RFCs, Internet). On Wed, Aug 24, 2016 at 6:28 PM, Arnaud Loonstra <[email protected]> wrote: > We like to relate to musical terms. We sometimes talk about orchestra or > composition. > > Rg, > > Arnaud > > On 2016-08-24 18:17, Andrew Hume wrote: >> >> thanks for the input. >> >> protocols are the wrong sort of thing, i think. that would be like >> saying another >> way to talk about the national highway system is to talk about the >> driving rules. >> (regardless of how important those rules, and protocols, in general, >> are.) >> >> after a quick read of teh FMC, the best term might be “compositional >> structure”, >> but thats uglier than communications web (i think). >> >>> On Aug 24, 2016, at 9:04 AM, Andriy Drozdyuk <[email protected] [3]> >>> wrote: >>> >>> Protocols? >>> >>> The FMC folks use "channels" to describe this kind of stuff: >>> http://www.fmc-modeling.org [4] >>> >>> Sounds like you might benefit from a "system map": >>> http://www.fmc-modeling.org/fmcbook [5] >>> >>> On Wed, 24 Aug 2016 at 11:31 Andrew Hume <[email protected] [6]> >>> wrote: >>> >>>> in discussions within my group, we often refer to the complete >>>> data flows between the various >>>> parts of a distributed application as a “communication web”. >>>> this includes a bunch of different >>>> stuff, including (but not limited to) normal zeromq links, >>>> pub-sub connections, broker-mediated >>>> links, job queues. >>>> >>>> technically, this is more like a directed graph of data flow. >>>> >>>> the term “communication web” is clumsy at best. are there >>>> better terms we could use? how do people on >>>> this list describe the data flow parts of their architectures? >>>> >>>> andrew >>>> >>>> _______________________________________________ >>>> zeromq-dev mailing list >>>> [email protected] [1] >>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev [2] >>> >>> _______________________________________________ >>> zeromq-dev mailing list >>> [email protected] [7] >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> >> >> >> Links: >> ------ >> [1] mailto:[email protected] >> [2] http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> [3] mailto:[email protected] >> [4] http://www.fmc-modeling.org/ >> [5] http://www.fmc-modeling.org/fmcbook >> [6] mailto:[email protected] >> [7] mailto:[email protected] > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
