-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e6d2934
commit e593744
Showing
1 changed file
with
26 additions
and
0 deletions.
There are no files selected for viewing
26 changes: 26 additions & 0 deletions
26
architecture-decisions/0002-synchronization-via-rabbitmq.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# 2. Synchronization via RabbitMQ | ||
|
||
Date: Archaeological | ||
|
||
## Status | ||
|
||
Accepted | ||
|
||
## Context | ||
|
||
We want Pomegranate to be a separate application from Figgy, but need some way | ||
for Figgy to tell Pomegranate about new resources so that when something is | ||
marked Complete in Figgy or taken down that it's reflected in Pomegranate. | ||
|
||
## Decision | ||
|
||
Figgy will send create/update/delete messages to a fanout RabbitMQ Exchange. | ||
Pomegranate will register a durable queue which listens to that exchange and | ||
process messages using [Sneakers](https://github.com/jondot/sneakers). | ||
|
||
## Consequences | ||
|
||
* If Sneakers workers stop processing, then new documents don't make it in to | ||
Pomegranate and we have to perform a reindex. | ||
|
||
* We have to monitor the status of our queues to make sure things are working. |