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: CSOs struggle with hidden threats, job stress
- US CERT BlueKeep warning: we got remote code execution
- DNS hijacking grabs headlines, but it’s just the tip of the iceberg
- Becoming more than human: My take on the advancements of Machine Technology
- SecurIT 2019: In an increasingly-encrypted world, visibility is more important than ever