API REST GraphQL

RAML мне не нравится тем, что он contract-first. Мне больше импонирует написать сервер и получить от него (всегда актуальную) документацию автоматически.

http://www.programmableweb.com/news/how-to-design-great-apis-api-first-design-and-raml/how-to/2015/07/10

https://github.com/jeffknupp/sandman REST API for databases

https://news.ycombinator.com/item?id=9927771 REST API for PostgreSQL

http://wiki.tcl.tk/41587 TCL/TK

http://www4.in.tum.de/~blanchet/api-design.pdf

http://overapi.com/

http://restcookbook.com/

http://habrahabr.ru/post/251193/ REST API

http://habrahabr.ru/post/252237/

http://habrahabr.ru/post/251669/

http://stateless.co/hal_specification.html JSON+HAL

http://www.reddit.com/r/Python/comments/3bntj3/ripozo_a_tool_for_quickly_creating_hateoasrest/

http://www.reddit.com/r/programming/comments/360cuf/do_you_really_know_why_you_prefer_rest_over_rpc/

http://apihandyman.io/do-you-really-know-why-you-prefer-rest-over-rpc/

http://developers.lyst.com/2015/02/20/1-to-1-relationships-and-subresources-in-rest-apis/

http://thelig.ht/callbacks/

http://amberonrails.com/move-fast-dont-break-your-api/

http://blog.heavybit.com/blog/apiary-api-design-versioning-testing

http://www.drdobbs.com/article/print?articleId=240169069&siteSectionName=web-development

https://github.com/tlhunter/consumer-centric-api-design e-Book

http://blog.mashape.com/list-of-40-tutorials-on-how-to-create-an-api/

http://www.reddit.com/r/Python/comments/25qqrp/resource_on_api_building_generally_but/

http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

http://codesuppository.blogspot.com/2014/04/how-to-create-hardened-api-for.html

http://kapeli.com/dash http://kapeli.com/docset_links

http://devdocs.io/

http://zealdocs.org/

https://zapier.com/learn/apis/

http://pyvideo.org/video/366/pycon-2011--api-design--lessons-learned

http://www.infoq.com/api/

http://www.infoq.com/api-design/

http://sendgrid.com/blog/quickly-prototype-apis-apiary/

http://jodoglevy.com/jobloglevy/?p=5

https://blog.apigee.com/taglist/rest_api_design

https://news.ycombinator.com/item?id=7735141

http://writings.quilt.org/2014/05/12/distributed-systems-and-the-end-of-the-api/

http://www.apigility.org/

http://apiblueprint.org/

https://news.ycombinator.com/item?id=7005348

https://github.com/pksunkara/alpaca

http://www.leaseweblabs.com/tag/javascript/

http://info.apigee.com/Portals/62317/docs/web%20api.pdf

http://habrahabr.ru/company/SECL_GROUP/blog/204510/ REST API

GraphQL

https://learngraphql.com/

https://medium.com/@clayallsopp/graphiql-graphql-s-killer-app-9896242b2125#.kyg39sibt

https://facebook.github.io/relay/docs/thinking-in-graphql.html

http://engineering.facile.it/graphql-an-introduction/

https://github.com/graphql/graphiql

https://news.ycombinator.com/item?id=10351949

https://medium.com/@gregoryziegan/how-graphql-taught-me-to-code-client-apps-1c631a9953bd

https://medium.com/@scbarrus/graphql-is-the-king-long-live-the-king-r-i-p-rest-cf04ce38f6c#.vlopai748

http://www.quora.com/APIs/What-are-the-best-resources-on-designing-a-good-API

http://37signals.com/svn/posts/3018-api-design-for-humans

http://www.apiacademy.co/

http://blog.parse.com/2013/10/02/parse-developer-day-video-series-how-to-design-great-apis/

http://aurisc4.blogspot.com/2013/11/how-to-make-good-api.html

http://piwik.org/blog/2008/01/how-to-design-an-api-best-practises-concepts-technical-aspects/

http://java.dzone.com/articles/how-design-good-regular-api

https://ep2013.europython.eu/conference/talks/good-api-design

http://mattgemmell.com/2012/05/24/api-design/

http://www.fastcolabs.com/3019805/designing-great-apis-means-valuing-laziness

http://blog.programmableweb.com/2012/02/14/three-ways-to-think-about-api-design/

http://blog.apiaxle.com/post/signs-youre-veering-from-good-api-design/

C++

http://lucumr.pocoo.org/2013/8/18/beautiful-native-libraries/

REST

http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

https://habrahabr.ru/post/323010/

https://medium.com/@schneidsDotNet/restful-api-best-practices-and-common-pitfalls-7a83ba3763b5#.7j4k6gc3q

https://bourgeois.me/rest/

http://blog.mwaysolutions.com/2014/06/05/10-best-practices-for-better-restful-api/

https://developer.github.com/v3/

http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

https://news.ycombinator.com/item?id=8618243

http://www.restapitutorial.com/lessons/whatisrest.html

http://www.restapitutorial.com/resources.html

https://restful-api-design.readthedocs.org/en/latest/

http://wsme.readthedocs.org/en/latest/ WSME

http://scotch.io/bar-talk/designing-a-restful-web-api

FLASK

http://blog.miguelgrinberg.com/category/REST

http://pyvideo.org/video/2668/writing-restful-web-services-with-flask

https://blog.apigee.com/detail/restful_api_design_nouns_are_good_verbs_are_bad

http://tonsky.livejournal.com/285268.html

http://www.infoq.com/articles/rest-api-on-cqrs

http://habrahabr.ru/post/204958/ REST is stateless

http://blog.northerntest.se/temp-slug-44/ testing rest with python request

http://habrahabr.ru/post/158605/

http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api?hn

http://www.youtube.com/watch?v=hdSrT4yjS1g

EVE (based on Flask)

http://python-eve.org/index.html

https://habrahabr.ru/post/276731/

http://restcookbook.com/ https://news.ycombinator.com/item?id=5469538

https://github.com/nicolaiarocci/eve

https://habrahabr.ru/post/276731/

http://blog.smartbear.com/software-quality/bid/254971/understanding-soap-and-rest-basics

http://slant.co/topics/what-is-the-best-architecture-for-building-a-web-service/opinions/rest

http://www.reddit.com/r/programming/comments/169p2d/soap_vs_rest_for_web_service_architectures/

http://en.wikipedia.org/wiki/Representational_state_transfer#RESTful_web_services

http://www.bitnative.com/2012/08/26/how-restful-is-your-api/

http://info.apigee.com/Portals/62317/docs/web%20api.pdf

http://blog.apigee.com/detail/restful_api_design/

http://blog.mugunthkumar.com/articles/restful-api-server-doing-it-the-right-way-part-1/

http://habrahabr.ru/post/144011/

http://www.infoq.com/presentations/REST-API-HATEOAS

http://rest.elkstein.org/

HTTP PUT == create new object

HTTP GET == read object

HTTP POST == update object

HTTP DELETE == delete object

http://quoderat.megginson.com/2007/02/15/rest-the-quick-pitch/?hn

All objects in REST have a URI. So, every defect in the system has a unique URI. Queries have unique URIs, etc.. If I want to update some defect, I POST an XML document to that defect's URI. If I want to delete a particular defect, I issue an HTTP DELETE request to that URI, etc.

Book

http://wiki.apidesign.org/wiki/APIDesignPatterns