Lobste.rs

60 readers
0 users here now

RSS Feed of lobste.rs

founded 9 months ago
MODERATORS
1
 
 
2
 
 
3
 
 
4
 
 
5
 
 
6
 
 
7
 
 
8
 
 
9
 
 

Usually, in an event-driven architecture, events are emitted by one service and listened to by many (1:n). But what if it’s the other way around? If one service needs to listen to events from many other services? I know many people would then use a command - for a command a n:1 relationship, i.e. a service receiving commands from many other services, is quite natural. Of course that’s not event-driven anymore then. Or is it.. what if the command doesn’t require a response? Then again, why is it a command in the first place, maybe we can have n:1 events instead? What’s your experience with this, how do you solve it in your system if a service needs to listen to events from many other services? Comments

10
 
 
11
 
 
12
 
 
13
 
 
14
 
 
15
 
 
16
17
 
 
18
 
 
19
 
 
20
 
 
21
 
 
22
 
 
23
 
 
24
 
 
25
 
 
view more: next ›