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.
- ISC updates critical DoS bug in BIND DNS software
- Android malware that can infiltrate corporate networks is spreading
- Firefox blocks websites with vulnerable encryption keys
- Ransomware spreads through weak remote desktop credentials
- Travis Perkins uses Splunk’s flexible cyber security monitoring to protect against customer data breaches