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.
- Microsoft's $25k AI challenge: predict which Windows PCs will be infected with malware
- The evolving threat landscape – What to look out for in 2019
- Supermicro third-party motherboard audit finds no spy chips
- Google+ leak affects 52 million users and G Suite users
- Microsoft's big Windows Defender ATP update: bad macros, fileless malware and faster response