I don't think this is OT at all. I know those articles and if even Martin Fowler says starting with a monolithic app is not too bad for most problems one should think twice before splitting up everything in tiny pieces.
At the end one needs to re-learn a lot. And due to this I think it is especially challenging doing microservices with technologies that power the average web app (Rails, Django, etc). Maybe it will help to choose a technology stack that emphasizes the values of microservices more (thinking of Clojure or Erlang).
I have the feeling you cannot go anywhere these days without hearing about how amazing Microservices are. I'm pretty sure it is not the silver bullet everybody is looking for ;-) But still, the idea is compelling. For me one problem with microservices is the orchestration, coordination or whatever you want to call the way they interact with each other. The folks at Giant Swarm have come up with an idea how to tackle this problem. Backed by Docker you have the facility to create apps composed of those microservices.
At least for me it was a good way to dive into microservices and Docker. Bonus: They super nice and very open to feedback :-)
WRK is a nice tool that can bring you quite far, for sure. But what about the orchestration of complex sessions? As I understood that blog post mentioned in another comment StormForger was actually able to play a game. A simple one, but there is still a lot of complexity involved.
But even if you can build something like this with WRK (which should be possible, due to the Lua support) you still need to setup your test environment (reproducibly), collect all the logs from the machines involved, monitor the test generators, create useful metrics from the test results and make it possible to interact with them. And I'm pretty sure I forget a whole bunch of stuff that needs to be done.
And I know, that I don't want to do all this stuff by myself. With a service providing all this, I can concentrate on the real work: Interpreting numbers and fixing problems ;-)
BTW: I'm pretty sure under the hood there is some load testing tool deployed. Cannot imagine someone runs such a large scale test without such thing.
At the end one needs to re-learn a lot. And due to this I think it is especially challenging doing microservices with technologies that power the average web app (Rails, Django, etc). Maybe it will help to choose a technology stack that emphasizes the values of microservices more (thinking of Clojure or Erlang).