Viewing profile — mwitkow

We use Thanos to provide the observability features (monitoring in particular) to Workers (i.e. user processes we run on our Cloud) that perform the simulation. You can have multip…

(disclaimer: I work at Improbable) The reason why we built Thanos was to enable monitoring of large scale simulation systems, which are inherently stateful, such as the Survival de…

That sounds very much what we're doing, except our microservice stack is in Go. For nodeJS you probably want to front your pods with grpcwebproxy ( https://github.com/improbable-en…

Totally agreed. There are cases where you basically want to deal with well structured web resources: HTML, images etc. For these, HTTP is a perfect fit. What we're replacing with g…

There's actually a stand-alone proxy that translates the REST mappings of `google.api.http` into gRPC requests. It relies on code-generation: https://github.com/grpc-ecosystem/grpc…

We haven't tried using gRPC in Python, as we have completely migrated from Python away towards Go. Our experience of using gRPC in Java, C++ and Golang is pretty good. While it had…

Yea, we actually work closely with the gRPC-Web team at Google to make sure our implementations are interoperable and we have plans for cross-integration-testing.

One of the authors here. This is indeed our own implementation of the pending spec. We are in touch with the gRPC team to make sure that their (still unreleased) implementation is …

That's interesting, we have a slightly related architecture. SpatialOS Runtime, itself distributed across many machines, acts as your "Master Control Process". It orchestrates Work…

Seems like an issue with skillsmatter/vimeo :( If you're interested, we also went to CoreOS Fest Berlin this year, where I presented how we dynamically reconfigure our SpatialOS si…

Our Platform team uses Golang extensively. We use it together with gRPC to form our microservice stack that orchestrates the SpatialOS simulations. The TL of our Platform API team …