[MGNLHOOK-22] (Event System) Events Pub/Sub model (queue, publishers, subscribers) Created: 12/Apr/22 Updated: 31/May/22 Resolved: 31/May/22 |
|
| Status: | Closed |
| Project: | Magnolia Webhooks |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Javier Benito | Assignee: | Javier Benito |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||
| Epic Link: | Configure a Webhook event | |||||||||||||||
| Sprint: | DevX 11 | |||||||||||||||
| Story Points: | 3 | |||||||||||||||
| Description |
|
Timebox SP: 3
This task is about to evolve the current events solution already present in the module, to a Pub/Sub model. The current solution uses an InMemoryQueue, implemented ad-hoc which relies on a Java BlockingQueue. It would be good to use a different, maybe more scalable approach, for example:
But having into account that at this point, given the time that we have, it's preferred to have something in memory than, for example, a queue service or similar. |