Microservices : Event-Driven with Spring Cloud Stream - Message Router | Function Routing - PT-01

Event Routing or Message Router: is the ability to route an event or message to a particular destination based on some conditions.
Github link for producer: github.com/Pas...
Github link for consumer: github.com/Pas....
In this series, we will be talking about Microservices patterns associated with Event-Driven Architecture. We will also talk a little bit about Domain Driven Design (but not our focus). In this series, we will create a business case related to Loan Mortgages. We will have some microservices to accomplish this use case. We will cover topics like:
Publish-Subscribe Pattern (vs Point-to-point)
Domain-Driven Design
CQRS, Event-Sourcing, Transaction Outbox Pattern, Command vs Event, DLQ
Test Coontainer
Spring Cloud Contract, etc.

[@ShishankAgrawal]

One question, if there are also rest controllers in our application which have servlets mapped with the URL you are proving in the postman, who well handle that request? the rest controller or the event handler.

[@juliogroth2454]

Hi, I think that you should create a method to handle it. And redirect to this method the processing of rest endpoint and events.
Is that @bayonnesensei8281?

[@prodigalScindian]

Awesome content, thank you for this helped a great deal. Question: does function definition have to be "functionRouter" or can we call it anything we like ? Reason I asked is if I try with any other name value then it doesn't kind of work. So wanted to find if functionRouter is a reserved value for this case

[@bayonnesensei8281]

Yes, exactly. As far as i know it should be functionRouter. I'll be investigating it with the Spring Team.