This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles Low This article has been rated as Low-importance on the project's importance scale.

I'm unhappy with the separation between design pattern and architecture pattern for the broker pattern. From my perspective is the Broker pattern too big to be considered a design pattern, e.g. I would say that I'm using an observer design pattern to fulfill the broker pattern. But everywhere, as soon as we talk about the publish / subscribe pattern, we see directly "it is implemented through the broker pattern". I find this reductive in many ways. Broker has a Many to One To Many relationship where the Publish / Subscribe pattern has a Many to Many relationship. Where the "One" can fulfill some expectation, in the Many to Many, every participant carries a certain level of responsibility What are your thoughts? Sebastianpfischer ( talk) 21:20, 7 January 2023 (UTC) reply