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.
- Attack, detection metrics improve but security specialists warn against complacency
- Ignorant of cybersecurity risk, breached small businesses are concealing the cost of recovery
- IBM: 4 billion online records were leaked in 2016
- Trojan source code leak poised to spur new online banking attacks
- Privacy advocates plan to fight Congress' repeal of ISP privacy rules