I performed the exact opposite migration at $DAYJOB recently - swapping an inter... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		mappu on March 19, 2020 \| parent \| context \| favorite \| on: RPC Olympics – The Search for the Perfect RPC Prot... I performed the exact opposite migration at $DAYJOB recently - swapping an internal text-based protocol to HTTP (over a local IPC pipe). The main benefit was we could suddenly reuse all the codegenerated routers/docs/authentication from the HTTP ecosystem. It significantly simplified/standardised our IPC layer and reduced the "weirdness" in the codebase.

pathseeker on March 19, 2020 [–]

Yep. Unless you're doing thousands of requests per second+, the right RPC protocol is likely just HTTP due to the massive improvement in mature tooling, debugging, etc.

cogman10 on March 19, 2020 | [–]

Today's toasters can handle 1k http requests per second. :)

The overhead of Http (especially 2/3) matters so little on modern hardware.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact