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.
- The week in security: Breaches growing, DDoS fiercer, mobile malware “negligible” as battlefronts shift
- Faster Internet access means more cyberattacks for Africa
- Gurucul identifies cloud threats based on identity, behaviors
- Google, WordPress, LastPass, Salesforce - new USB token secures them all
- Attacks against industrial control systems double