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
Posts Tagged: change
Uniting publishers and subscribers, WebSub has become a well-adopted method for updating content on the internet. Since the protocol can be used for any data type accessible via HTTP, it’s a popular method for communicating notifications and changes, and is a great alternative to the constant server polling of the past. 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
Change is inevitable and growth is a good thing. When your API has reached the point of expanding beyond it’s original intent and capacity, it’s time to consider the next version.
Whether that next iteration is a whole number version bump or just a feature expansion, it’s important to consider the pros and cons of how you let your developers know about it. Read more