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.
- After MongoDB, ransomware groups hit exposed Elasticsearch clusters
- WhatsApp vulnerability could expose messages to prying eyes, report claims
- Suspected NSA tool hackers dump more cyberweapons in farewell
- Guccifer 2.0, alleged Russian cyberspy, returns to deride US
- Siblings arrested in Italy's worst cyberespionage operation ever