This blog post presents a diagram of a possible headless CMS architecture with search that uses a brokerage architecture for webhooks and API calls.
Rather than repeating the information, for a better understanding of this diagram and the intentions of this architecture, please see the following posts, the last of which presents an architecture that is almost identical but uses an event system.
- Centralizing [Headless] [CMS] Data Access – Deliverystack.net
- Web Service Brokerage Architecture [for Headless CMS] – Deliverystack.net
- Integrating Event Systems with Headless CMS – Deliverystack.net
- Headless CMS with Event System Diagram – Deliverystack.net
Without the event system, the brokerage service calls webhooks in process orchestration rather than publishing events. Process orchestration calls brokered APIs that may invoke webhooks in external systems.
If anything other than CMS publishing needs to pass data to content delivery, it needs to call the broker to invoke webhooks in the content delivery environment.
Custom UI extensions cannot poll the event system to update the browser.
If you have any comments on this architecture or diagram, please comment on this blog post.