{"id":780,"date":"2013-03-08T10:53:14","date_gmt":"2013-03-08T09:53:14","guid":{"rendered":"http:\/\/www.alkannoide.com\/?p=780"},"modified":"2013-06-14T17:08:38","modified_gmt":"2013-06-14T15:08:38","slug":"rest-cookbook","status":"publish","type":"post","link":"https:\/\/www.alkannoide.com\/2013\/03\/08\/rest-cookbook\/","title":{"rendered":"REST cookbook"},"content":{"rendered":"
A new small blog post where I sticked informations or links about Rest<\/a> and\u00a0Restful<\/a> :a style of architecture for distributed softwares. This post will be updated each time I have new links.<\/p>\n Restful is stateless.\u00a0The main goals of Restful architecture are scalability, availability and agnotiscs technologies between software (via an common interface).\u00a0A new Internet draft is out, it names\u00a0RESTful Authentication Pattern<\/a>\u00a0and will help to design your architecture.<\/p>\n If you will deploy this type of architecture, you can read this slideshare which give best practices to design API<\/a>\u00a0(a webinar is available too).\u00a0To design a Restful architecture, you need to design your URI<\/a>. There is another good document made by Apigee<\/a>\u00a0: Web API Design<\/a> – Crafting interfaces that Developers love [PDF file]<\/p>\n Here is some examples of API architectures:<\/p>\n