APIs are invoked through a uniform interface that references resources through URIs and operations through HTTP methods. The italicized words in the numbered principles are the abbreviated terms often ...

RESTful design anti-patterns Far too often, you will see a supposedly RESTful system in which the designers have shoehorned every permutation of their API into a POST invocation. Just because you ...

We demonstrate how to build a RESTful API on top of CQRS systems. The result joins HTTP semantics and REST style with distributed computing concerns such as eventual consistency and concurrency.

REST stands for Representational State Transfer, is more open in how it is coded, and is the more common type of API. You’ll often see them described as RESTful APIs too.

Changes to a RESTful API are inevitable. However, unless you adhere to the best practices and ensure that the API is backward compatible, your changes can break the API’s compatibility with ...

Solr has a HTTP/JSON-based API. However, it isn’t exactly a REST API because it doesn’t really follow any of the rules for a well-defined REST interface. I whine about this sometimes.

Had we restricted RAML to purely-RESTful APIs, it would have 1) not applied to almost any existing APIs, and 2) not been feasible for most API initiatives to adopt today.

APIs seem to be everywhere these days. Every popular online service has one. APIs allow developers to interact with online services without actually having to point and click their way through a UI.

REST was introduced as a lightweight solution to address the burdens of SOAP. However, it turns out that a RESTful API needs a schema to define the contract and make it more discoverable.

By understanding API design patterns, and following best practices, you can create APIs that are reliable, scalable, maintainable, and easy to use.