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.
- Sitting ducks for cybersecurity breaches, small businesses get new options
- GCHQ: change your passwords now even if Uber says it contained the breach
- Christmas rush brings great deals to online shoppers – and new risks for their employers
- Dell, Lenovo, HP will patch hundreds of devices affected by Intel's buggy embedded CPU
- As unencrypted data becomes “negligence”, business leaders are taking encryption strategy away from IT