4 ms·

>So how would you operate each of these bespoke services? One service uses TCP, one uses UDP, one uses SCTP. What happens if your buffer sizes are incorrect? S

by adev_ 6y ago

>So how would you operate each of these bespoke services? One service uses TCP, one uses UDP, one uses SCTP. What happens if your buffer sizes are incorrect? Such bullshit. Since when we use UDP for a CRUD service ? Since when SCTP is even considered outside of the telecom world? HTTP and Rest-like API have been able to handle properly simple CRUD API since 20 years without problems, way before gRPC was even a thing. gRPC has its usage for large, complex API that required a proper RPC framework. But in 99% of the case, yes it's an overkill.

worik 6y ago
"HTTP and Rest-like API have been able to handle properly simple CRUD API since 20 years without problems, way before gRPC was even a thing." There is the problem. "Twenty years old? How can that be any good" is a common POV in my experience
Karrot_Kream 6y ago
> Such bullshit. Since when we use UDP for a CRUD service ? Since when SCTP is even considered outside of the telecom world? You're making a strawmam out of this. I'm responding to the following: "while I have developers that have written full Node.js sites and dont know that IP or a Port, or TCP, UDP, is..." But thank you for the insult. > HTTP and Rest-like API have been able to handle properly simple CRUD API since 20 years without problems, way before gRPC was even a thing. Hm, what are you talking about? Are you talking about the client? Are you talking about a load balancer? I don't think anyone is proposing that a simple static blog use gRPC to serve content to its users. > But in 99% of the case, yes it's an overkill. Compared to what? I'd argue that CRUD over HTTP is wrong. In fact, folks have been writing CRUD over TCP for ages. Why do we need to massage CRUD syntax over HTTP when we can just stream requests and responses over TCP? In fact, TCP predates HTTP by 20 years, so if you're using the historical argument, raw TCP is even older. How much bullshit is there around AJAX and Websockets and HTTP multipart and HTTP keep-alive when we're just trying to recreate TCP semantics? So why are you drawing the line at HTTP? Seems arbitrary to me.

by adev_ 6y ago

worik 6y ago

"HTTP and Rest-like API have been able to handle properly simple CRUD API since 20 years without problems, way before gRPC was even a thing." There is the problem. "Twenty years old? How can that be any good" is a common POV in my experience

Karrot_Kream 6y ago

> Such bullshit. Since when we use UDP for a CRUD service ? Since when SCTP is even considered outside of the telecom world? You're making a strawmam out of this. I'm responding to the following: "while I have developers that have written full Node.js sites and dont know that IP or a Port, or TCP, UDP, is..." But thank you for the insult. > HTTP and Rest-like API have been able to handle properly simple CRUD API since 20 years without problems, way before gRPC was even a thing. Hm, what are you talking about? Are you talking about the client? Are you talking about a load balancer? I don't think anyone is proposing that a simple static blog use gRPC to serve content to its users. > But in 99% of the case, yes it's an overkill. Compared to what? I'd argue that CRUD over HTTP is wrong. In fact, folks have been writing CRUD over TCP for ages. Why do we need to massage CRUD syntax over HTTP when we can just stream requests and responses over TCP? In fact, TCP predates HTTP by 20 years, so if you're using the historical argument, raw TCP is even older. How much bullshit is there around AJAX and Websockets and HTTP multipart and HTTP keep-alive when we're just trying to recreate TCP semantics? So why are you drawing the line at HTTP? Seems arbitrary to me.