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.
- Schneider Electric PLC simulator flaw exposes workstations to hacking
- Friday's IoT-based DDoS attack has security experts worried
- US transport agency guidance on vehicle cybersecurity irks lawmakers
- Blockchain, IOT pose risk and security headaches if privileged accounts aren’t controlled
- Lyft customers face potential hack from recycled phone numbers