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.
- Ashley Madison misled users with a fake security award
- Epic Games forum hack underscores the need to install security patches
- Imperva: Application layer DDoS attacks are on the rise.
- Groups oppose US plan to collect social media info from visitors
- Alleged NSA hackers probably gave away a small fortune by leaking exploits