3 ms·
This anecdote highlights scope creep and mismanagement, not a fault of gRPC.
by PaulWaldman 2y ago
This anecdote highlights scope creep and mismanagement, not a fault of gRPC.
- ivancho 2y agoI think the anecdote highlights that there's no incremental way to approach gRPC, it's not a low risk small footprint prototype project that can be introduced slowly and integrated with existing systems and environments. Which, well, it is a bit of a fault of gRPC.
- perezd 2y agoI think that's not true. There are plenty of incremental ways to adopt gRPC. For example, there are packages that can facade/match your existing REST APIs[1][2]. Reads like a skill issue to me. [1]: https://github.com/grpc-ecosystem/grpc-gateway https://github.com/grpc-ecosystem/grpc-gateway [2]: https://github.com/connectrpc/vanguard-go https://github.com/connectrpc/vanguard-go