Move WebSocket broker configuration into externalized service
Closed this issue · 1 comments
gregturn commented
- When in dev mode, use in-memory broker configuration.
- When in production mode, delegate to externalized broker, like RabbitMQ to ensure multiple clients are ALL receiving WebSocket messages.
gregturn commented
No longer needed due to https://github.com/gregturn/spring-a-gram/blob/master/spring-a-gram-backend/src/main/java/com/greglturnquist/springagram/backend/SpringDataRestEventHandler.java#L108-L112, which pipes backend updates to the frontend over RabbitMQ.