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.
- WIN a HTC Vive Kit valued at $1399, take this 3 minute survey for your chance to WIN!
- Participate in this market research and go into the draw to win a Lego Death Star, (valued at $999).
- 6 cities | 20 exhibitors | International & local keynotes | Hear from Mark Loveless 'Simple Nomad' & Jeff Lanza Former FBI - Save your seat at CSO Perspectives Roadshow
- Answer 5 quick questions and you could win a Lego Mindstorm EV3, (valued at $499).
- How Cosabella is using martech to win the retail battle
- Report: It’s the era of experience but don’t forget the basics
- Dendy, Legg Mason appoint new marketing leaders
- Medibank CEO: We're getting better at customer experience
- Velocity frequent flyers program strong performer in mixed half-year for Virgin