Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

12
  • Not sure why there's a close vote for "opinion based." There are many, many named patterns and architectures in software engineering, and if the thing I describe does not have a common name, that is also not an opinion. Commented Aug 6, 2020 at 6:57
  • 1
    It is also (quite specifically) not a request for a recommendation. Could those voting to close please provide some specifics? If terminology questions are off-topic here, is there a Stackexchange site where they are not? Commented Aug 6, 2020 at 7:05
  • 1
    I dared to slightly edit your question in order to make clear that you are not asking for resources but asking for terminology corresponding to a specific design, and why this terminology matters. Hope this helps. Commented Aug 6, 2020 at 9:51
  • @Christophe Thank you! I agree, it's much clearer. Commented Aug 6, 2020 at 9:56
  • 1
    You explicitly ask how this pattern is named - but a pattern is just a name, and you're presuming that this is a well-known named pattern. I don't think that a generic (typed) message queue + a registry of handlers is sufficiently special and exotic to need its own Proper Noun Pattern Name - it's just a message queue, a mapping from message type to handler(s?), and simple event loop. You haven't shown the argument serialization or the handler interface, so I can't tell if that's doing something special. Commented Aug 6, 2020 at 10:36