3 ms·
Fine if you control the clients and the servers, but if you're writing your API for public consumption, API customers want REST not gRPC.
by chrismmay 7y ago
Fine if you control the clients and the servers, but if you're writing your API for public consumption, API customers want REST not gRPC.
- DrScientist 7y agoYes REST has a lower bar to entry. However, if you need to you can provide REST end points from a gRPC definition. eg https://levelup.gitconnected.com/grpc-basics-part-2-rest-and-swagger-53ec2417b3c4 https://levelup.gitconnected.com/grpc-basics-part-2-rest-and... We had the pleasure of working with some legacy SOAP recently - the other end had changed the WSDL such that our client no longer compiled from the WSDL - they couldn't work out what was wrong and where fearful of changing it again so we had to had to hand roll the client. Fun times.... I hope neither get as complex as SOAP - one of potential pitfalls of tooling is it becomes 'free' to add complexity.
- chrismmay 7y agoOur product literally exists to present a single simple interface to consolidate and orchestrate across dozens of SOAP interfaces. We handle the complexity so customers don't have to. So I'm glad SOAP exists and is much more complex than REST.