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.
- Hacktivist group possibly compromised hundreds of websites
- Report: Every company is compromised, but most infections not yet at critical stage
- One third of enterprise iOS devices vulnerable to app, data hijacking attacks
- Austrian court dismisses class action suit against Facebook
- FBI alert discloses malware tied to the OPM and Anthem attacks