API management is a necessary but boring practice. As developers make use of a mix of public cloud, purchased or open source libraries, and homegrown services, the number of APIs used by developers quickly renders pouring through documentation impractical.
Microservices, usually accessed via RESTFul APIs, cause API calls to rapidly proliferate. Even modest-sized microservices-based systems experience API overload quickly. Agile development can exacerbate the problem of understanding and using APIs. The rapid pace of Agile, especially Scrum, leaves little time for proper documentation of APIs. Documentation often takes a back seat to continuous deployment.
Please register or log into your Amalgam Insights Community account to read more. Log InRegister
I’ve been asked a lot over the past couple of weeks what I’m planning to do over the rest of my career. (Apparently, nobody expects you to retire at 40…) I believe that Amalgam Insights is going to provide a base to pursue what is going to happen next in the world of technology. But to explain what that means, first, I need to take a step back.
I’ve spent most of the past 20 years of my life considering how the future of applied technology will change the way that we evaluate our environments, conduct work, and better understand the world that we live in. In the mid-90s, when both personal computing and the Internet were coming into ascendancy, I was fortunate to have multiple experiences introducing me to the combined power of these technologies: Continue reading “The Battle for Context – Hello World!”