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.
- Help us better understand the trends and major practices related to technology use in STEM education. Take this two minute survey NOW.
- APJ businesses think they will be breached: Here's why: Read the article NOW
- F5 Security Hub NEW Look - Try us out today!
- More than 270,000 customers worldwide trust Fortinet to protect their businesses. Learn more.
- NEW Gigamon Transform Security Zone - Find out more now!
- CMO's top 10 martech stories for the week - 27 May
- How this marketer got a traditional manufacturing business to embrace digital
- David Jones marketing chief departs; digital executive role created
- Mercer CMO: How B2B brands can achieve customer love
- Pure Storage CMO's tips to make your marketing resonate