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.
- Ad fraud Trojan updates Flash Player so that other malware can't get in
- Cisco leaves key to all its Unified CDM systems under doormat
- Integrate encryption with device management to overcome key-management issues: LANDESK
- Plex hacker demands Bitcoin ransom for return of data
- Telcos, government agencies least trusted to protect Australians' privacy