I’ve done a lot of thinking on versioning for an API I’ve been working on. I feel that the mystical nature of API versions should not be the last consideration of an API implementation - why do that to yourself; why do that to your customers?
So how does one approach versioning for the “Programmable Web?” What do your users do when they come to a fork in road?
Approach it using basic considerations of any API architecture (not holding true to Zachman’s approach - we’ll handle the where, when, and why some other day).
In Development at Fellowship Tech, one thing we’ve been working on is an automated build pipeline. This allows us to build our software and deploy it to our environments with no human intervention. The complete automation of our builds and deployments is called a deployment pipeline or build pipeline. It’s called a pipeline because once the build is inserted into the pipeline, a set of mostly automated process act upon it and pending the passing/approval of the results of that process it moves on to the next stage. Let’s examine the stages of the build process.
- User Case Story from Hope Community Church
October 28, 2013
- Group Search Categories and More
October 21, 2013
- Account Creation
August 7, 2013
- Single Sign On Functionality Exposed
June 25, 2013
- 3rd Party App Showcase
March 22, 2013
- API Communication Value Changes
November 2, 2012
- API Enhancement: Create and Edit Groups!
August 13, 2012
- API Enhancement: Requirements Exposed
June 25, 2012
May 23, 2012
- Resource Versioning
April 24, 2012
- Enter Visitor Data via Your Church Website
March 16, 2012
- Fellowship One & Planning Center Online
March 1, 2012
- API Libraries and Sample Code
February 7, 2012
- Building a custom login for your church website using the API
November 29, 2011
- Roll Foward!
August 9, 2011
- The Agile Triangle
July 27, 2011
- Conversation Paralysis
July 7, 2011
- Picture this, image updates & creates through the REST API
May 10, 2011
- A REST API double shot : Groups and Events realms
May 9, 2011
- Increasing Software Delivery by 500%
May 3, 2011