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.
- Top PC vendors bloatware undermine Windows 10 security
- Australia's cybersecurity maturity, infrastructure protections lag US by “large gap”: ACCS
- Macquarie-Optus venture targets cybersecurity education at business, academia
- OEM software update tools preloaded on PCs are a security mess
- Laptop updaters riddled with security holes