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.
- Fixing Australia’s “backward” national cybersecurity posture requires “fresh thinking” on skills, resources: ACSC
- Deal in the works? BlackBerry delays Pakistan retreat by one month
- Flaws in Huawei WiMax routers won't be fixed, researcher says
- Data breach of toy maker VTech leaked photos of children, parents
- The week in security: Root-certificate stuff-ups send Dell, device makers scrambling