Don't you think, maybe, thinking of a pack of wolves tearing away at a dead carcass, or a kitty coming to your outstretched hand, a flock of colourful macaw parrots flying in the Amazonian basin is more friendly than a dryly spoken PointToPointChannel, PublishSubscribeChannel and CompetingConsumers in camel case?
It is understandable that application programmers demand simplicity. As they need to implement these patterns, why not change the name?
More colourful, yes, but I couldn't see the reason behind the names immediately. "Dry" terms that actually happen to _describe_ their behaviour are immediately grasped and understood.
I understand that perhaps colourful and friendly names can be fun, but I suspect you'd have a hard time getting these accepted among the people that actually use the protocol.
maybe - but I found I could perfectly understand each pattern by relating the analogy of the fun colourful names to the behaviour of the problem. Well at least I can say it worked for me ;)
I walked away from the AMPQ design specs, feeling a bit tense. Though I immediately grasped restms.org meaning. I think it is well written, describing the point accurately and in brevity. Once you clone the repo, there are more docs in there which are quite a good read - specifically the restms_developers.txt doc.
Which goes into "Reverse Housecat", "Multimaster Housecat", "Wolf Call"... I can't say they are obvious at first glance.
Metaphor is great for explaining things - and as a guide. Those names might make a great sidebar. I just don't see the need to rename things when it's a firmly established domain.
maybe A grade Technical Officers can grasp this technology easily, but actually there is a majority of B grade and C grade CTO. These are the guys who will set the trend of a technology. In other words it isnt the programmer who chooses the technology. This article is written for the B grade and C grade CTO to understand....