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.
- Fake Telstra and EnergyAustralia email bills spread banking trojans
- Gone in 15 seconds: why faster bank transfers make Australia an even bigger target for email fraud
- Synchronized security is the right arsenal for modern CSOs: Sophos exec
- Study finds shoddy kids' smartwatch security give parents anything but peace of mind
- Google launches key-locked Gmail for targeted users