Solace Community is getting a facelift!
On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.
We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!
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
Categories
