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.
- Lavabit developer has a new encrypted, end-to-end email protocol
- Researchers propose a way to use your heartbeat as a password
- Spanish police nab suspected hacker behind Neverquest banking malware
- Trump nominee suggests IRS cybersecurity and staffing boosts
- Google pushed developers to fix security flaws in 275,000 Android apps