Put your API on a JSON diet
See the original posting on JavaWorld
Last week I discussed design considerations for APIs, given that APIs arent applications and shouldnt be treated as such. At small scales, APIs that come along for the ride with bulky Web frameworks might be fine, but beyond that youre asking for trouble. If youre building an API that will serve a large number of clients, your API code should be thin and tight, as well as make liberal use of caching. Otherwise, the future headaches will be crippling.
But this doesn’t pertain to the foundation of your API only; it’s relevant within the API itself. Here, putting your JSON on a diet can be crucial.