Switch to RabbitMQ #97
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Agony Forge is designed to be deployed into AWS using DynamoDB and "Amazon MQ" but I've run into a problem with that. AWS's support for ActiveMQ has fallen behind, and Apache has released a new version called Artemis. AWS doesn't support Artemis, but Spring Boot 3 no longer supports versions prior to Artemis. The starter package
-activemqhas no updates for Spring Boot 3 and there's a new-artemisstarter instead.So I'm stuck: I can't upgrade to Artemis because AWS doesn't have it, and I can't keep using ActiveMQ because Spring Boot 3 doesn't support it. The answer seems to be switching to RabbitMQ where AWS has a fairly recent version and the Spring Boot 3 support is there. It has a STOMP connector and it seems to be functionally equivalent so far.
If you would rather use ActiveMQ I have left the configuration in
docker-compose.yamlfor it with an explanation. It still works fine for me in Docker. Any other message broker that supports STOMP should work just fine too. The thing that really ties Agony Forge to AWS is DynamoDB.