3 ms·
Overengineering is a slippery slope. And the reality is that in 99% of cases, you don't need it. If there's a single data value that needs a flexible JSON payl
by crazygringo 4y ago
Overengineering is a slippery slope. And the reality is that in 99% of cases, you don't need it.
If there's a single data value that needs a flexible JSON payload, then just put that as an encoded string in your GET/POST parameter. It's not "inconsistency", it's just a special case. Same as you might not need a floating point number anywhere except for one endpoint. Not a big deal. You don't need to migrate the entire call to JSON-RPC.
- rerdavies 4y agoHow do you return data?
- wruza 4y agoIn my opinion, overengineering is putting JSON into a URL or exposing data as a resource and putting a URL parameter to it in a URL only to avoid an actual request body, for some unclear reason. I believe all the described tactics come from a static html limitations territory where it makes sense to put continuation data in hrefs to avoid forms and javascript.