Moving Beyond a Single API Developer Portal

ICYDK: I am working with a number of different groups who are using developer portals in some very different ways — once they have moved beyond the concept that API developer portals are just for use in the public domain. With the introduction of the static site shift in the CMS landscape and the introduction of Jekyll and GitHub Pages as part of the GitHub project workflow, the concept of the API developer portal is beginning to mean a lot of different things, depending on what the project objective is.

An API portal is becoming something that can reflect a specific project or group and isn’t something that always has a public URL. Here are just a few of the ways in which I’m seeing portals being wielded as part of API operations. https://goo.gl/7NhDQW #DataIntegration #ML

RESTful APIs With the Play Framework — Part 2

In the first part of this series of articles, we talked about the main features of the Play Framework, its basic structure, and how to deploy our applications. In this part, we will talk about how to develop RESTful Services. If you remember (if not, we invite you to read the first part of this series of articles) we mentioned that Play Framework is Reactive, which means that we can develop Asynchronous and Synchronous Services. For the purposes of this second article, we will focus on Synchronous Services.

Developing Web Services

Let’s look in more detail at the index action in HomeController. https://goo.gl/gBGn5A #DataIntegration #ML