tysont

I led the engineering team at Fauna and this is false - we had a performance culture and performance managed/exited people when they did not meet expectations. I've managed some outstanding teams/organizations at Microsoft, Amazon, and Riot Games and the team behind Fauna was world-class; on par with the best teams that I have seen or been a part of. There are plenty of reasons that the company didn't succeed, some in our control and some out of our control, but the caliber of people at the company and the company culture are not on that list.

James Governor interviews Tyson Trautmann and Matt Freels from Fauna about the document-relational paradigm and the future of databases.

League sharded players to geographic regions and didn't allow matches between players in different regions. Geographic location wasn't a consideration in matchmaking otherwise AFAIK. I left Riot when Valorant was still under development and can't speak to how matchmaking works, unfortunately.

Nice catch! I investigated this today with the team and we realized that metrics from a dev environment (which isn't representative of our production topology) were being included in our status page internal latency graphs for the US/EU Region Groups. We addressed the issue - you can see the clean data on status.fauna.com.

To add a bit of color from the author, the content in the article was informed by my experience building distributed systems at Microsoft, Amazon, and Riot Games. At Riot we sharded our playerbase for a number of reasons (including complexity of matchmaking), but we may have chosen a different approach if we had a service like Fauna that could push data closer to players at the edge. With centralized relational databases, cross-region calls to load account info, entitlements, etc. would have been a very jarring experience in the client.

I've seen a number of database companies publish blog posts and put out tweets offering a competing point of view: that single-region is enough and multi-region doesn't matter. Would love to engage with that crowd here and get their perspective on the content in the blog post.