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.
- Supreme Court approves rule change that expands FBI computer search powers
- Developers leak Slack access tokens on GitHub, putting sensitive business data at risk
- ISIS cyberattack capabilities are unorganized, underfunded -- for now
- Estonian man gets over 7 years in prison for role in global DNS hijacking botnet
- FBI confirms it won't tell Apple how it unlocked terrorist's iPhone