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.
- Sustained attacks on Australian education reflect data’s continued vulnerability
- Google matches Apple's iOS bug bounty: will pay up $1.5m for a really tough Android Pixel hack
- Emergent Android banking Trojan shows app overlay attacks are still effective
- Firefox’s Mozilla doubles its bug bounty cash rewards
- Australian businesses slower to detect breaches than global peers, but everyone is still taking too long