Add RabbitMQ support with Spring Cloud
See original GitHub issueOverview of the issue
Currently, when a developer wants to use Spring cloud the default choice Apache Kafka as message broker. By default, Spring Cloud provides 2 binders: Kafka and RabbitMQ.
Kafka is an excellent Message broker but it’s overkill for small projects. Plus, it requires to manage zookeeper which is yet another component to maintain. RabbitMQ is a first-class message broker well known on the market.
Motivation for or Use Case
Reproduce the error
Related issues
Suggest a Fix
Most of the job is already done, after a first look it’s all about providing the appropriate dependencies and a bit of YAML config (< 10 lines of code).
JHipster Version(s)
JHipster configuration
Entity configuration(s) entityName.json
files generated in the .jhipster
directory
Browsers and Operating System
- Checking this box is mandatory (this is just to show you read everything)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:18 (17 by maintainers)
Top Results From Across the Web
Spring Cloud Stream RabbitMQ Binder Reference Guide
This guide describes the RabbitMQ implementation of the Spring Cloud Stream Binder. It contains information about its design, usage and configuration ...
Read more >Event Driven Microservices with Spring Cloud Stream and ...
As a result, this service requires only the Cloud Stream and Spring for RabbitMQ dependencies. Add a Component class to process the message....
Read more >Spring Cloud Stream with RabbitMQ: Message ... - Stack Abuse
In this article, we'll introduce you to Spring Cloud Stream, which is a framework for building message-driven microservice applications that ...
Read more >Messaging with RabbitMQ in Spring Boot Application
RabbitMQ is an open-source message broker that allows enterprise applications to communicate with each other. It's a popular AMQP (Advanced ...
Read more >Setting up RabbitMQ with Spring Cloud Stream | E4developer
Many developers are hesitant using them with the fear that they may add too much complexity and learning curve to the understanding of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@PierreBesson hsa promised I made a sample app with RabbitMq https://github.com/danielpetisme/jhipster-sample-app-rabbitmq
You’ll find 2 branches,
master
is the init of a monolith with Kafka support,binder-rabbit
is … the rabbitmq adapatation. The diff: https://github.com/danielpetisme/jhipster-sample-app-rabbitmq/compare/master...rabbit-binderI made a REST Endpoint
/api/messages
,topic-jhipster
destinationtopic-jhipster
destination and save it into a list I’ve added a rabbit routing key just for the sake of demo@deepu105 👍 Module or your external templates proposal could be next big architecture choice IMHO but it requires a core team decision. Without adopting an Apache or JavaEE (RIP) approach Jhipster could be a kind of meta-blueprint and core-team supported minimal feature. JHipster == orchestration between client, server, docker, db etc. and module are Angular, Spring, MongoDB, etc. Each module would be responsible of it’s integration. Rather than having a huge central code generator and a lof of
ifs
.Anyway, It’s not the purpose of this issue (even if it’s an interesting topic) so let’s close it right now I gave @PierreBesson a sample app we’ll see in the future months how things are moving forward.