I bet the correct answer is 3 nodes. That way, if one node goes down, the other two can have a heated debate about who's responsible while the events pile up.
2 nodes, definitely. Unless of course, you want to be the person who has to explain to the boss why the whole system crashed because one node went down.
I'm going to go with 4 nodes. Redundancy is great, but can you really call it an 'Events Service' if it doesn't have a whole development team on standby?
3 nodes? Overkill! With 2 nodes, you get high availability and failover. Anything more is just showing off, like a tech hipster with a 10-node Events Service.
Denae
1 months agoGail
1 months agoCelestine
10 days agoMyrtie
20 days agoMona
2 months agoJustine
2 months agoQuentin
16 days agoRosio
1 months agoMarkus
1 months agoChristiane
1 months agoCrista
2 months agoMarjory
12 days agoStaci
14 days agoAlysa
19 days agoKrystal
1 months agoFlorinda
3 months agoLore
3 months agoFlorinda
3 months ago