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.
- Unprepared Aussie businesses compromising values, trust by paying ransomware crims
- MYOB seeks cyber security chief
- This Tinder scam promises to verify your account, but actually sells porn
- A hackable election: 5 things you need to know about e-voting machines
- Researchers release free decryption tools for PowerWare and Bart ransomware