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.
- Apple patches iOS against potent zero-day spyware attack
- Informatica CEO: 'Data security is an unsolved problem'
- CrowdStrike finds a bridge to Google's VirusTotal
- 12 tips to help SMBs select and manage vendors
- How to get a job as a security engineer: skills, qualifications, responsibilities and salary