The life of an API follows a predictable lifecycle – from creation to deprecation, each stage of the API lifecycle denotes an important event, and it carries with it a set of best practices. API developers tend to think about the future in very positive ways – how the API will behave, what its design will be – but in doing so, they don’t always consider what the end of that API might look like. Read more
Posts Tagged: versioning
We interview William Lyon of Neo4j, a speaker at the upcoming Austin API Summit 2019.
William Lyon is a Developer Relations Engineer at Neo4j, the open source graph database. With experience working in several nimble startups, William’s current work is focused on GraphQL integrations — in fact, he’ll be joining our “Diving into GraphQL” LiveCast later this month. Read more
Release management is an important part of any API development lifecycle. That being said, it is also consistently overlooked, often considered more as an afterthought than a foundational element of the API and business environment. This is unfortunate, as implementing proper release management can not only prevent significant issues from arising, it can also improve the efficacy and value of your customer relationship management processes. Read more
The API industry thrives on change. As the needs of the consumer grows, so too do the demands on the API provider. Accordingly, providers are faced with the growing prospect of constant technological evolution.
While this cycle of change is largely a positive one, it does bring with it some unique challenges; one such challenge is that of communicating change to your developer users. Read more
Some people, when confronted with a problem, think “I know, I’ll use versioning.” Now they have 2.1.0 problems.
If your software has a fuzzy or seemingly random versioning scheme — or no apparent version number at all — you’ll likely agree it can be a nightmare to work with. Read more