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.
- Mobile users 'more likely to be struck by lightning' than infected by malware
- Government-private sector collaboration vital for cyber security: Brandis
- Talking ’bout my generation – the next wave of infosec
- Australia's online ads less fraudulent but lower quality than elsewhere
- Project Fi will help Google amass even more data about you