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.
- Kentucky workers comp carrier survives ransomware
- APT3 hackers linked to Chinese intelligence
- APAC’s transformation enthusiasm causing “scary things” to happen with IoT security
- Former NSA chief weighs in on cybersecurity, cyberespionage at ZertoCon
- Malicious subtitles in popular media players could lead to remote compromise