4 ms·
Writing a book on this subject would be a fairly pointless exercise as it will age very quickly. You would be better off looking for "how we did xyz" type of bl
by huhtenberg 9y ago
Writing a book on this subject would be a fairly pointless exercise as it will age very quickly. You would be better off looking for "how we did xyz" type of blog posts from notable sources.
There are also academic-style papers from Amazon's team on creating high-reliability systems and such. These are worth a read too.
- onion2k 9y agoWriting a book on this subject would be a fairly pointless exercise as it will age very quickly. The technology that we use to implement APIs changes but the fundamental reasoning doesn't. A book about building APIs doesn't really need to talk about specific technologies. Personally speaking, I think the principles that drive the design of APIs I build today are the same as the principles I was using 20 years ago; plan your data structures, include extensible structures for future unknown things, don't make anything trivially enumerable, use HTTP verbs consistently, and document the hell out of everything with working examples that have automated tests so you can easily fix them when the API changes. If you do all that you should end up with a nice API.
- huhtenberg 9y agoYeah, sure. But all this adds up to more like a skinny pamphlet rather than a book.
- afarrell 9y agoThere need to be more skinny pamphlets with concise good advice in the world.