Etcd, or, why modern software makes me sad

Re:Etcd, or, why modern software makes me sad by EdwardDiego on Tuesday July 14, 2020 @10:31PM (#23840550)

> But you can't curl the state of your infra component without creating a program and downloading the client artifacts.

You can if you enable server reflection[1] and use a tool like grpcurl[2].

[1]: https://github.com/grpc/grpc-java/blob/master/documentation/... [2]: https://github.com/fullstorydev/grpcurl

[ Parent | on HN ]

Re:Etcd, or, why modern software makes me sad by yc12340 on Tuesday July 14, 2020 @11:00PM (#23840737)

> tool like grpcurl

Not available in any repositories and largely unknown to general masses (much like gRPC itself).

Personally I like gRPC and sometimes use it in projects. But the author is right — attempting to gradually replace an existing HTTP API via gRPC API is like replacing horses with genetically modified cows. You need a very... corrupt mindset to ever attempt anything like that.

[ Parent | on HN ]

Re:Etcd, or, why modern software makes me sad by abernard1 on Tuesday July 14, 2020 @11:12PM (#23840795)

So... being a comment from that "guy" that made the original comment :-)

To reemphasize the problem with grpcurl.... it's _still_ static. You must download the artifact. It's like needing a different phone for every person you call (protobuf artifacts) instead of calling different people on the same phone (same artifact, different address and data in payload).

[ Parent | on HN ]

Re:Etcd, or, why modern software makes me sad by EdwardDiego on Wednesday July 15, 2020 @02:27AM (#23841988)

shrug Was just pointing out that you don't need the .proto files on hand to interact with a gRPC service if you use the above approach.

[ Parent | on HN ]