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.
- Ignore that call from “Apple” about an iCloud breach
- Want more clout with the CEO? Wait until your first ransomware attack.
- Consultant urges never pay ransomware demands
- Apple: Macs and iPhones are safe from newly revealed CIA exploits
- Google Play faces cat and mouse game with sneaky Android malware