Last week I discussed design considerations for APIs, given that APIs aren't applications and shouldn't be treated as such. At small scales, APIs that come along for the ride with bulky Web frameworks might be fine, but beyond that you're asking for trouble. If you're 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.
- Microsoft adds conservative release 'ring' to Windows 10 beta program
- 6 things you should know about Twitter's timeline change
- Browser maker Opera's board urges sale to Chinese collective for $1.2B
- LG's G5 smartphone to have 'always on' ability
- Microsoft delivers Office 2016 to subscribers on the slow train