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.
- How to protect your business from online payments fraud
- Executives are overconfident about the sophistication of their DevSecOps automation
- Can Senseon beat Darktrace at its own game with its 'AI triangulation' technology
- Most European companies failing to meet GDPR obligations
- Security, insurance providers want to help you evaluate your cyber risk