🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Sequential consumers call for single request pushed in topic- Solace Rest API (RDP- Consumer)
Use Case: Sequential consumers call for single request pushed in topic Insurance Quote creation -> Activity Creation -> ActivityCreated->SMS/Email
For above use case you are basically looking if Solace can act as an microservice and decide to move to next step if the previous step is successful. Meaning, if Insurance Quote is Created Successfully then only Activity Created message should be triggered and so on till the end.
Answers
-
Hi @rakesh,
The Solace Event Brokers will route events between publishers and subscribers, but they do not allow you to execute logic onboard the broker itself. What you are doing sounds very much like what folks used to use ESBs for (orchestration), but in general these days we recommend the use of choreography in your EDA using microservices and having "Smart Endpoints and Dumb Pipes". Note that your "smart endpoints" could be custom microservices, flows in an iPaaS, a single FaaS, or whatever you prefer!
I'd highly recommend taking a look at this white paper to understand some of the differences and benefits of choreography vs. orchestration: https://solace.com/blog/microservices-choreography-vs-orchestration/
Hope that helps!
0
