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.
- CSO Roadshow 2018: How do we build a secure IoT?
- Outlook.com and Hotmail block all state govt email after hijacked account sends 8 million spam messages
- VirusTotal lets devs check whether a legit app will wrongly be flagged as malware
- The Humble Cybersecurity Bundle offers everything you need to protect your PC for $15
- Olympic Destroyer destructive malware targets EU bio-weapons research groups