API versioning made simple: Use linear versioning only, then clone your API when you meet a different need In my opinion, branching of APIs (aka a minor version living in parallel with a “newer” major version) is to be avoided. The typical reason for needing branching is that in-progress changes will not be deployed fast enough... Continue reading API versioning made simple
API protocols can and should be based on the best choice for their purpose and audience, and not all APIs are REST based. Importantly the choice of protocol also implies a choice of fundamental API design abstraction. For example, REST based interfaces are resource-based while SOAP interfaces are method-based. Such differences must be taken into... Continue reading The basics of good API design
Health providers need to access many resources to provide the best care possible. This includes engaging the patient in the care plan, improving collaboration across multiple health related entities (i.e. partners), and accessing data resources to improve diagnosis. While providing all this they need to meet security and regulatory requirements, make frequent improvements to services... Continue reading Healthcare Providers – A Prescription for APIs
A common myth is “SOAP is dead; APIs are always REST.” Granted, REST is the currently most popular protocol for easily consumable APIs. But nothing in the concept of an API requires it to be based on a particular protocol. And there are reasons why the industry has invented more than one protocol in the... Continue reading Making the case for SOAP based APIs
[soundcloud url="https://api.soundcloud.com/tracks/185975481"] Continue reading ‘APIs and Mobile/Electronic Payments’ with Jason Harmon, Session 1
In the last few years, the enterprise landscape has changed. While IoT “infestation” is a major reason for this change, there are other important reasons too. The need to provide flexible interface for your partners in a quick manner, the need to mobile enable not only any new application/process that is being built, but also... Continue reading Where are you spending your enterprise IT dollars?
Some say that APIs are all you need. Others that Services are indispensable. In the end, it is not a matter of APIs or Services. It is not a matter of an API gateway or an Integration Bus. You need both to unleash the power of combining the insight from your backend systems with the... Continue reading Are APIs all you need?
Today’s low temperature at my house is -1 oF (-18 oC) with a wind chill of -25 oF (-32 oC). This got me thinking about APIs for Utilities. The old joke is “everybody complains about the weather, but nobody does anything about it.” Well, maybe we can’t change the weather, but perhaps... Continue reading APIs for Utilities: Let’s do something about the Weather!
Ole Lensmar (CTO/ SmartBear - SOAPUI) and I are doing a webinar on “Enterprise API readiness” tomorrow at 11 am EST. Registration details inside. Continue reading IBM/SmartBear Webinar – Tomorrow (Jan 8, 2015) 11 am ET
APIs should have their own simple, light weight lifecycles. The API owner should be able to declaratively decide what an API looks like, with whom to share that API, and under what terms and conditions. All done independently of the lifecycle of software assets providing data and function exposed through the API. We must trust... Continue reading Manage your APIs like content, not like software