3 ms·
Spinning this a slightly different direction: think about what their API operation model is, and how well it lines up with your current and (more importantly) e
by majormajor 9y ago
Spinning this a slightly different direction: think about what their API operation model is, and how well it lines up with your current and (more importantly) expected future use cases?
If you expect that you might need to significantly change what you're doing in the future, having a more simple, composable model around resources that you can call as you need might save your ass down the line compared to if they model things as specific RPC use cases and you find yourself needing a particular variation they don't support out of the box.