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.
- The week in security: Cybercriminals eyeing new opportunities from cryptocurrency miners
- Intel says it's been hit with 32 separate lawsuits over Spectre, Meltdown
- Security lessons from the 2018 Pyeongchang Winter Olympics
- From banks to Bitcoin: Trickbot shifts online hustle to cryptocurrencies
- Don't panic about the new 'Prime' Meltdown and Spectre CPU exploits