Riot Games Messaging Service

That&#x27;s am impressive bit of technology, and nice to see it&#x27;s making extensive use of Erlang (we&#x27;re using Elixir).<p>I&#x27;d be interested to know if the service works across multiple regions though. Some of the biggest challenges we&#x27;ve faced when engineering our realtime platform has been in having no single point of congestion and effectively peer-to-peer routing within the cluster. This is not that important if all your servers can be in a single region, however if you want your users in Australia for example to have a similar latency profile to those in USA, then clients in Oz need to connect to servers in Oz and all routing for customers in Oz does not need to traverse continents for other customers in Oz, but does for customers in US. I&#x27;d be interested to know if that was tackled in the design. Michal you following this thread?<p>Matt Ably realtime - <a href="https:&#x2F;&#x2F;www.ably.io" rel="nofollow">https:&#x2F;&#x2F;www.ably.io</a>

I realize the article isn&#x27;t actually about a chat service, but I continue to be confused because there exists Riot[1], the messaging client of the Matrix network.<p>[1] <a href="https:&#x2F;&#x2F;riot.im&#x2F;" rel="nofollow">https:&#x2F;&#x2F;riot.im&#x2F;</a>

Edit: Upon more careful reading, it appears that a response is sent from the server to the client via WebSocket which contains the resource and method that the client can request using HTTP if it wishes to update.<p>Original question: Can someone explain to me why the JSON message sent to the REST interface seems to contain URL and Type as data?<p>Is it because they are transmitted using web sockets but the concepts of &quot;resource&quot; (ie: clubs&#x2F;v1&#x2F;clubs&#x2F;665632A9-EF44-41CB-BF03-01F2BA533FE7) and &quot;method&quot; (ie: GET) still just make sense and happens to be very similar to HTTP?

Nice to see yet another game studio making use of Erlang.

This article reminds me of a previous HN post. The program discussed was called pushpin or pinpush.<p>These solutions are the glue between stateless and stateful services. I guess they will become increasingly important as some services specialize towards responsiveness. The use websockets or http2 without giving up the simplification provided by restful architecture.

wondering why they have the edge nodes and not just a load balancer. looking at their responsibilities it looks like a lot of the overlap with the responsibilities of a load balancer.

Their JSON have an key called payload which saves a String rather than an Object, is there any benefits to doing this? since they also escape the &quot; in the String

I&#x27;d like to see more info on their customized Erlang&#x2F;OTP mnesia . michalptaszek mentioned it in the comment: <a href="http:&#x2F;&#x2F;disq.us&#x2F;p&#x2F;1gltwfs" rel="nofollow">http:&#x2F;&#x2F;disq.us&#x2F;p&#x2F;1gltwfs</a>

Do people use zeromq for this kind of work? It seems the various socket types are tailored to building such load balancing and routing architectures, but I&#x27;m not aware if zeromq is in use at this scale.