InfoQ Homepage API-Design Content on InfoQ
-
Taming Dependency Hell within Microservices with Michael Bryzek
Michael Bryzek, co-founder and ex-CTO at Gilt, discussed at QCon New York how ‘dependency hell’ could impact the delivery and maintenance of microservice platforms. Bryzek suggested that dependency hell may be mitigated by making API design ‘first class’, ensuring backward and forward compatibility, providing accurate documentation, and automatically generating client libraries.
-
Founder of API Blueprint Discusses Progress
API languages are in their infancy and API developers are actively using API Blueprint, RAML, and Swagger. Together, as a community, developers are defining the standards that will be used in the future. InfoQ recently had the opportunity to talk to Jakub Nesetril, creator of the API Blueprint project and CEO of Apiary.
-
Apigee API Studio: Designing, Testing and Sharing APIs
Apigee has opened up API Studio, a free online tool for creating, testing and sharing APIs.
-
A Look at MongoRepository for .NET
Most of the open source projects we share with you on InfoQ increase the capabilities of another library or technology. MongoRepository is different in that it intentionally limits the capabilities of the underlying library. We’ll let Rob Janssen why it does this in his own words.
-
API World 2014: Summary of Day One Events
In this news item, we summarize the highlights of various talks from day one of the conference which are primarily focused on the craft of designing and developing effective APIs.
-
Apigee-127: A Toolkit for Authoring APIs and their Services
Apigee has put together a number of open source tools for creating APIs and a number of related service.
-
Heroku’s HTTP API Design Guide
Wesley Beary, a member of the API team at Heroku, has compiled a list of guidelines for creating HTTP+JSON APIs presented in a condensed form here.
-
APIs.json: Publishing and Discovering APIs
APIs.json lets domains make their APIs public and discoverable by search engines.
-
Layer 7 Survey - Strong Growth Predicted for Hypermedia APIs
Layer 7 recently released the results of a survey focussed on API design and deployment. The survey showed that API designers are divided on security versus usability as their top priority, there is an even split between XML and JSON representations and strong growth is predicted for Hypermedia style APIs. In summary the survey showed there is no one-size-fits-all way to manage APIs.
-
Anypoint for APIs: An Interview with Uri Sarid
MuleSoft recently released a significant upgrade to their Anypoint platform for APIs which brings together API design, collaboration and API management features. InfoQ interviewed MuleSoft CTO, Uri Sarid to find out more about the platform.
-
Getting the Avengers with Marvel Comics API
Recently, Marvel has made available a public API and a RESTful service which provides access to their comics metadata.
-
The API Orchestration Layer
The traditional resource-oriented API model may not satisfy the most important of your API consumers. Daniel Jacobson of Netflix asserts that good API design is about knowing your API consumers and optimizing your API for that audience.
-
The Human Aspects of API Design: An Interview with Apiary's Jakub Nesetril
API Design and description is more than just a technical interface contract between machines. Apiary's Co-Founder and CEO Jakub Nesetril points out that the real consumer of an API description is the developer, with all the concerns of engagement, usability and communication that entails. We spoke with Jakub recently about Apiary's approach to API design and emerging API tools and workflows.
-
MuleSoft Open Sources RAML Tools for Designing RESTful APIs
MuleSoft has just announced the release of three RAML-based tools for designing, evaluating and testing RESTful APIs.
-
Mike Amundsen Workshop on API Design
"Don't version unless you absolutely must, and it is rare that you absolutely must" says Mike Amundsen in a series of API design workshops he held recently. Amundsen describes the "USE" paradigm for API design focussing on usability, scalability and evolvability. He describes the three most common styles of API implementation and how they compare to these principles.