I appreciate that the engineers at Spotify wrote this post, but not because it's a novel solution or because most software engineers don't know this stuff (well

I appreciate that the engineers at Spotify wrote this post, but not because it's a novel solution or because most software engineers don't know this stuff (well, some don't I suppose). However, I find it and others like it helpful to engineering groups that exist outside of tech companies. Why? It gives those groups and their technical leads something to point to when discussing trade-offs, timelines and investments in technology with product teams or more senior engineering leadership whom might not have had a background in software engineering and architecture. "Don't take my word for it, look at what the engineers at Spotify, et. al. wrote about this topic." Public service notice: Employing these patterns in small companies that don't have any need for the complexity is an anti-pattern.