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.
- The NSA reportedly tried -- but failed -- to use a Stuxnet variant against North Korea
- Google levels up security at I/O with secure comms tool, better authentication
- New NSA phone dragnet proposals blasted as flawed
- Tor connections to hidden services could be easy to de-anonymize
- How Google took a page from Apple to secure Android Pay