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.
- Former Hacking Team developer reportedly in contact with a terrorist group
- Black Hat 2015: Cracking just about anything
- Ad group urges FTC to reject right to be forgotten in US
- Banks balance security and workflow when encrypting in the cloud
- Neiman Marcus case a reminder to check your cyber coverage