Some day, someone might write an authoritative book about this aspect. Let's call that inevitable book Event Centric as a placeholder title (this is a quote...)
71
stars
7
forks
source link
Problem / suggestion: Comparison of event driven architecture v notification v pull on demand #23
We have a number of ways in which systems / domains / garbfangles communicate - event carried state transfer, change feed or notifications, pull on demand being three I can think of.
Are there any others?
What are the advantages / disadvantages of each - why would you choose one over another - and what do you need to do around each of these choices?
We have a number of ways in which systems / domains / garbfangles communicate - event carried state transfer, change feed or notifications, pull on demand being three I can think of.
Are there any others?
What are the advantages / disadvantages of each - why would you choose one over another - and what do you need to do around each of these choices?