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.
- App security suffering as survey finds that most developers still aren't building for mobile
- Board-level cyber-resilience must look far and wide – and right up to the top
- Intel: Criminals getting better at data exfiltration
- Businesses failing to enforce mobile security on BYOD Apple users: survey
- The Web's ten most dangerous neighborhoods