Conference Materials

API Abstraction & API Chaining

API abstraction is the separation of cross cutting concerns related to the api to better enable externalization to architectural services.

Shared I/O State in Distributed API Architecture

The 'old' API pattern binds I/O (communication functionality) to business logic by binding I/O state (request/response data). We solve through abstraction and synchronizing the data.

Grails API Toolkit

Since Grails was going to be a 'Convention over Config' plugin for the Spring-boot microservice framework, the first release of the tools were released as a plugin for the Grails framework knowing I could easily convert the libraries when the Spring-boot conversion took place.

The New API Pattern

The API pattern was created in the 1970's when 'distributed architectures' didn't even exist and was established mainly for 'centralized architectures' as it bound the communication data/logic to the business logic. This is a rewrite of the API pattern for distributed systems.

Videos

API Abstraction & API Chaining

The SpringOne 2014 presentation on 'API Abstraction & API Chaining'

Shared I/O State in Distributed API Architecture

The SpringOne 2015 presentation on 'Shared I/O State in API Architecture'

API Chaining (part 1 of 2)

A Quick video introduction into API Abstraction and API Chaining

API Chaining (part 2 of 2)

A Quick video introduction into API Abstraction and API Chaining

News & Articles

Why The API Pattern Is Broken And How We Can Fix It

Guest Article on the 'API Evangelist' Website on the architectural cross cutting concern and other issues that the API pattern creates.

Just Because Github Has a GraphQL API Doesn’t Mean You Should Too

Mike Stowe, the Developer Relations Manager of Mulesoft, wrote an article about his attempt at a 'partial implementation of API Chaining(tm) and how even just a partial implementation improved his speed by 66%!

API2Cart : Interview with Owen Rubel

An interview I was asked to do with API2Cart after a conference talk I did.