re: Why Event Sourcing is a microservice communication anti-pattern VIEW POST


Don't totally agree. If you use something like avro, and make sure the schema's are backwards compatible consumers can use the newer schema when they want/need.


See my answer concerning API evolution on Twitter:


I hope nobody thinks exposing your event sourcing events 1:1 to an external API is a good idea. Still evolution to the event sourcing objects should be controlled if used by multiple teams.

code of conduct - report abuse