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.
- Mass CCleaner malware attack actually targeted tech giants
- NotPetya costs FedEx $300m, now weighs up cyber insurance
- Pen-testing may pacify auditors, but it won’t stop hackers from taking your data
- As Equifax jettisons CISO and CIO, survey finds CISOs feel devalued by business leaders
- Chrome versus IE and Edge: which is more secure for enterprise?