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.
- Apple confirms iPhone-killing “Error 53,” says it’s about security
- Researcher finds serious flaw in Chromium-based Avast SafeZone browser
- Internet Archive's malware museum takes you back to the days of cheeky viruses
- Dridex banking malware mysteriously hijacked to distribute antivirus program
- As cloud rolls in, SunRice plants infrastructure seeds with security refresh