3 ms·
I'm trying to understand the problem this solves. Let's say you have an HTTP API which allows users to update their email address: POST /api/user/:usernam
by daveroberts 9y ago
I'm trying to understand the problem this solves. Let's say you have an HTTP API which allows users to update their email address:
POST /api/user/:username/update_email
But you change the application to require API clients to send the user_id instead of the username.
POST /api/user/:user_id/update_email
Wouldn't you still need to mandate that all clients are updated regardless of whether you use this tool as an abstraction layer to your API?
- warent 9y agoRecommend reading on what an RPC is: https://www.geeksforgeeks.org/operating-system-remote-procedure-call-rpc/ https://www.geeksforgeeks.org/operating-system-remote-proced... And protobufs: https://developers.google.com/protocol-buffers/docs/proto3 https://developers.google.com/protocol-buffers/docs/proto3 Example, one benefit is that you're defining your API by using language neutral protobufs which then generate code consistently (including types!) into many languages. Your entire communication procedure can be easily and succinctly described in a single small, human readable file.