Day: January 19, 2018

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/6PEMSK #DataIntegration #ML

ICYDK: Below we can see the code of the REST API that we defined on Enterprise Integrator: $1 { “status”: “success”, “statusMessage” : “Image Uploaded” }

Let us explain each part of the above code. https://goo.gl/rTWVJ5 #DataIntegration #ML

Multi-tenancy is a fundamental architecture that can be used to share IT resources cost-efficiently and securely in cloud environments in which a single instance of software runs on a server and serves multiple tenants.

It’s been years since we first heard about it; it came out again riding the wave of cloud computing, so we can assume that multi-tenancy is a consolidated architecture — and the benefits in terms of maintainability and costs are well-known. https://goo.gl/TQqJFF #DataIntegration #ML