News for hackers. Stuff that matters.
Re:Why We’re Switching to gRPC by _ZeD_ on Monday May 27, 2019 @03:23PM (#20024647)
hey, hey! have you known about this new "webservices" stuff? with SOAP you can call remote code as it is here! and with WSDL you can create automatically the client!
Re:Why We’re Switching to gRPC by adrianmonk on Monday May 27, 2019 @06:44PM (#20025776)
Short summary of web services:

Phase 1: Ad hoc, free-for-all chaos.

Phase 2: SOAP tries to bring order. It fails mainly because the "S" ("Simple") is a lie.

Phase 3: Pendulum swings hard toward simplicity with HTTP plus JSON plus nothing else, thanks.

Phase 4: Things shift possibly more toward the middle (a little structure), but none of the competing systems have become obvious winners.

Re:Why We’re Switching to gRPC by crehn on Monday May 27, 2019 @10:04PM (#20026629)
Most things in life seem to change like a pendulum learning from previous swings, slowly converging to a healthy middle. Extremes are useful since they give perspective and attractive since they're easy to grasp.
Re:Why We’re Switching to gRPC by Sevii on Monday May 27, 2019 @10:03PM (#20026628)
Except for the fun time when the WSDL doesn't match the actual implementation because 'they don't support WSDL'. (despite serving one from their SOAP service)
Re:Why We’re Switching to gRPC by tracker1 on Tuesday May 28, 2019 @01:33PM (#20032369)
Or worse, when the WSDL has a response type of "Object" ... OMG was this ever painful to generate clients for. Usually cheated and used Node as a bridge service.
Re:Why We’re Switching to gRPC by nullwasamistake on Monday May 27, 2019 @04:00PM (#20024878)
Man I miss WSDL. We're building it all over again with gRPC.
Re:Why We’re Switching to gRPC by docker_up on Monday May 27, 2019 @11:57PM (#20027108)
gRPC is exactly like XDR and ONC-RPCs from the Unix days of the 90s, ex. NFS.