3 ms·
Rest is great, but. We have something similar where I work and it has done great things for API consistency. But the efficiency of resulting implementations is
by teknopaul 5y ago
Rest is great, but. We have something similar where I work and it has done great things for API consistency. But the efficiency of resulting implementations is not good. We have no solution for simple task oriented apis like change-password. In these cases rest is fugly.
I'm still looking for some good API guidelines for rpc that are not resource oriented and don't accidentally result in hundreds of new methods.
- dopaminefasting 5y agoWhen you say you have no solutions for change-pass, what exactly is the stumbling block here. As for RPC guidelines, they match the same guidelines you'd have writing a native API as a set of interfaces. You already know how that works. Just apply it. If I'm wrong, let me know what's the issue.