Author: admin

ICYMI: The topic of API discovery has been picking up momentum in 2018. It is something I’ve worked on for years, but with the number of microservices emerging out there, it is something I’m seeing become a concern amongst providers. I’m also seeing more potential vendor chatter, looking to provide more services and tooling to help alleviate API discovery pain. Even with all this movement, there is still a lot of education and discussion to occur on the subject to help bring people up to speed on what API discovery is.

The most common view of what API discovery is is when you need to find an API for developing an application. You have a need for a resource in your application and you need to look across your internal and partner resources to find what you are looking for. Beyond that, you will need to search for publicly available API resources using Google, Github, ProgrammableWeb, and other common ways to find popular APIs. This is definitely the most prominent perspective when it comes to API discovery, but it isn’t the only dimension of this problem. There are several dimensions to this stop along the API lifecycle that I’d like to flesh out further so that I can better articulate across conversations I am having. https://goo.gl/gxE2GA #DataIntegration #ML

For as long as we have created software, we have tried to invent intelligent constructs for having our documentation automatically generated. Trolltech was one of the pioneers of this approach and later came tools such as Doxygen and the XML documentation in Visual Studio. The reasons are obvious: to make sure the software and its documentation are always “in sync." The Phosphorus Five solution is arguably the most dynamic of these approaches. See a screenshot of it below.

First of all, it doesn’t need any compilation or building process to occur to generate your documentation. In fact, as you choose to view the "meta information” for your documentation, the help system will automatically generate its documentation on the fly, not even caring to cache it. This has several advantages, one being that the documentation for your system is always “in sync” with your source code. If you delete a source code file or edit it, the documentation automatically updates itself accordingly. Below is a video demonstrating this. https://goo.gl/cnKsXg #DataIntegration #ML