Talk:Broker pattern
![]() | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
|
Dilemma for this architectural pattern
editI'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)