Re:How to Design Great APIs [video]
by AznHisoka on Wednesday October 02, 2013 @02:57PM
(#6484460)
How to design a great API:
1) Give me some very very valuable data that can help my business. (90% of it)
2) Ensure reliability and uptime (9% of it)
3) Make it RESTFUL and have good documentation (1% of it).
[ Parent
| on HN ]
If I'm writing a system library in C, I'm supposed to somehow make it RESTFUL?
It's weak, but you might consider strtok() to be less restful than strlen() because it isn't stateless.
I consider Mockito (a java library) to have a great API. Only your 3) applies to it.
I guess I was referring more to web services that provide data.
The I in API is for interface - 1 and 2 are just about having a great web service :)
Re:How to Design Great APIs [video]
by ianstormtaylor on Wednesday October 02, 2013 @06:04PM
(#6485725)
I'd consider Salesforce to have #1 and #2, but pretty sure no one who's used their API would call it "great".