On: Real-world HTTP/2: 400GB of images per day

[arca_vorago]

Aren't there more performant options than restful these days? Any particular reason why you didn't choose those?

Would that be a good case for websockets?

[runeks → arca_vorago]

There are definitely more performant options. I considered ZeroMQ for a while, and almost decided on it, but went for HTTP/REST because of the built-in error handling, and request-response style (as far as I can see, I would have to implement all of this if I chose to use ZeroMQ).

I also chose HTTP because, at the end of the day, I still get almost ~1000 payment per second after the change (on a laptop). VISA handles 200k payments/second at peak, so that's peak VISA levels on 200 MacBook Pros.

I see I might have misspoke when I said "front-end". It's really the front-end (logic part) of the backend server, which now comprises two parts: stateless logic ("front-end") and database (stateful) backend. So I haven't considered Websockets.

[xzyfer → arca_vorago]

H2's single long lived connection means it's a contender to replace websockets. As a bonus you get to use HTTP semantics.