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.
- Terror-suspect database used by banks, governments, has been leaked
- Mobile ransomware use jumps, blocking access to phones
- Researchers dismantle decade-long Iranian cyberespionage operation
- ACLU lawsuit challenges US computer hacking law
- Wormable flaws in Symantec products expose millions of computers to hacking