Tuesday, September 17, 2013

Eve: Python REST API Framework

Powered by Flask, MongoDB, Redis and good intentions Eve allows to effortlessly build and deploy highly customizable, fully featured RESTful Web Services
Check out the Eve homepage
Eve is an out-of-the-box, highly customizable and fully featured RESTful Web API framework that you can use to effortlessly build and deploy your own APIs

Eve is Simple

from eve import Eve

app = Eve()
app.run()
The API is now live, ready to be consumed:
$ curl -i http://example.com/people/
HTTP/1.1 200 OK
All you need to bring your API online is a database, a configuration file (defaults to settings.py) and a launch script. Overall, you will find that configuring and fine-tuning your API is a very simple process.
Eve is thoroughly tested under Python 2.6, Python 2.7 and Python 3.3.

Features

  • Emphasis on REST
  • Full range of CRUD operations
  • Customizable resource endpoints
  • Customizable, multiple item endpoints
  • Filtering and Sorting
  • Pagination
  • HATEOAS
  • JSON and XML Rendering
  • Conditional Requests
  • Data Integrity and Concurrency Control
  • Multiple Insertions
  • Data Validation
  • Extensible Data Validation
  • Resource-level Cache Control
  • Versioning
  • CORS Cross-Origin Resource Sharing
  • Read-only by default
  • Default Values
  • Predefined Database Filters
  • Projections
  • Event Hooks
  • Native MongoDB Support
  • SQL Alchemy Support (WIP)
  • Powered by Flask

Wednesday, July 31, 2013

Why REST is so important

http://babdev.blogspot.co.at/2013/07/why-rest-is-so-important.html

This post is dedicated to REST, an architectural style of shaping webservices and the most misunderstood concept in the history of IT. This post is addressed to you who is designing webservice apis not being fully aware what REST actually means.

The meaning of REST

Why RPC is a pain in the A**

But SOAP is still bad

Sessions are Evil

Dont reinvent Hypermedia

http://babdev.blogspot.co.at/2013/07/why-rest-is-so-important.html

Monday, April 22, 2013

An Overview of REST Metadata Formats

Although the REST community initially took a stance against metadata for REST APIs, a number of metadata standards have none-the-less emerged over the last couple of years, mainly fueled by the need to document APIs for their consumers.

...

The common goal of current metadata formats for REST APIs is to specify
  • Entry point(s)
  • Resource paths
  • Methods to access these resources (GET, POST, PUT, etc.…)
  • Parameters that need to be supplied with these methods (Query, Template, HTTP Header, etc.)
  • Formats of inbound / outbound messages/representations (JSON Schema, XML Schema, Relax NG, etc.)
  • Status codes and error/fault messages
  • Documentary information (descriptions, etc.) for all these
All these are somewhat derived from the principles underlying REST APIs – i.e. those of resources, representations etc. Non-functional aspects of APIs, like for example authentication (Basic, OAuth, SAML, etc.), security (encryption, signatures, etc.) and versioning are unfortunately still poorly addressed by most REST metadata standards. This is where the WS-* standards “shine”, but it is also what many refer to as WS-(death-star) – indicating the complexity of the WS standards that might ultimately lead to their demise. Hopefully the REST community will align around common standards and best practices more successfully than vendors did in the SOAP-domain around 10 years ago.
...

Secure Your REST API... The Right Way

Secure Your REST API... The Right Way:
At Stormpath we spent 18 months researching best practices, implementing them in the Stormpath API, and figuring out what works. Here’s our playbook on how to secure a REST API.


Brian Sletten on RESTful API Design

Brian Sletten on RESTful API Design:
Brian Sletten, the author of the DZone REST Refcard dispels pre-conceived notions about REST API design while going over Representation Design, Versioning, and more...



Designing a Beautiful REST+JSON API

Designing a Beautiful REST+JSON API:
In this presentation, Les Hazlewood - Stormpath CTO and Apache Shiro PMC Chair - will share all of the golden nuggets learned while designing, implementing and supporting JSON-based REST APIs, using examples from a clean real-world REST+JSON API built with Java technologies.