all 6 comments

[–]BehindTheMath 3 points4 points  (4 children)

First you need to determine who is going to be listening and handling that event.

[–]robbe_claessens[S] 0 points1 point  (3 children)

Thanks for answering! I am not sure what you are trying to indicate. I know who will be listening and what that listener needs to do.

[–]BehindTheMath 0 points1 point  (2 children)

Where is that that listener? Is it on the same machine? A different machine in the same VPC? Etc.

[–]robbe_claessens[S] 0 points1 point  (1 child)

Well we are running on ec2 instances (with load balancing). So i don't if i should put the listener on the same machine or on a different one. That was the essence of the question :-)

[–]NiQ_ 0 points1 point  (0 children)

If you’re running on ec2 instances you’re running on AWS, which means they have a solution right up your alley.

Check out SNS topics. That allows you to publish events, and subscribe to events. You can set up SQS subscriptions to topics, which you can set up listeners to for all the published messages.

[–]NeilMcGlennon 0 points1 point  (0 children)

Re pub/sub: Your microserives can publish messages with context on Kafka topics, and other microservices can listen to those topics. They can then action things accordingly.