Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21f00305a065645

Jump to content

Talk:Broker pattern

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 3 years ago by Sebastianpfischer in topic Dilemma for this architectural pattern

Dilemma for this architectural pattern

[edit]

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