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.
- Trump hotel chain fined over data breaches
- The week in security: Yahoo breach biggest hack ever; Australia leads APAC in reported breaches
- Largest DDoS attack ever delivered by botnet of hijacked IoT devices
- NY regulation aims to raise bank security standards
- Here's what you should know, and do, about the Yahoo breach