One thing that has been a big win (which isn't mentioned in the article) is the concept of "duplication of data". Our microservices are currently listening to everything and only taking action on things they care about. As such, they are also storing data about things they care about.

I couldn't agree more with this statement. I wish I'd gone into this, I was trying to cover a lot here about our new architecture in general.

In the beginning of development, our throughput was dreadful, but now that we have all the tools in place, adding a new service or handler of an event in a service is incredibly fast.

Yeah, we're adding a lot of new functionality and handlers really fast now. The great thing is when we need to split a service out into a new service we simply grab all the handlers for that event and the new service is pretty much already in a proof of concept state!

On top of that, it also makes it easy for front end interfaces to be designed with a mock microservice (or handler) that simply emits it for their testing with a backend developer going through and filling it. As long as the API isn't overly complex for emitting events, almost anyone on the team can do this.