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.
- Russia claims it foiled a cyber attack from a foreign spy service
- Researchers find a way bypass the iOS activation lock
- Remote management app exposes millions of Android users to hacking
- ‘Distributed guessing’ attack lets hackers verify Visa card details
- AI is coming, and will take some jobs, but no need to worry