> There are no 'nice to haves' That's an assumption, there's a lot of assumptions flying around right now. The simple answer is we don't know. Often there are

> There are no 'nice to haves' That's an assumption, there's a lot of assumptions flying around right now. The simple answer is we don't know. Often there are a lot of design tradeoffs, bcrosby was likely questioning whether all events going into that specific queue were strictly necessary for matchmaking. We don't even know that this was actually the problem. So far, no professional post-mortem, or root cause analysis has been released. There are certainly ways one can setup these type of services so they dynamically scale correctly, but since the architecture they are using isn't fully disclosed its difficult to say anything with certainty and this type of guesswork is entirely unproductive.