ICYMI: 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/5xWWGL #DataIntegration #ML
ICYMI: 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/5xWWGL #DataIntegration #ML
ICYDK: In this blog, we will build an Azure Logic App using the YouTube connector as a trigger and the Outlook connector as action.
Prerequisite
*
Microsoft Azure Subscription – Sign up for Azure Free account https://goo.gl/RDNN5L #DataIntegration #ML
DNS is one of those shadowy things that tends to be managed by a select few wizards, and the rest of an organization doesn’t have much knowledge, awareness, or access at this level. APIs has shifted this reality for me and this is something I’m also seeing at organizations who are adopting a microservices, and DevOps approaches to getting things done. DNS should be a first-class citizen in the API toolbox, allowing for well-planned deployments supporting a variety of services, but also allowing for logging, orchestration, and, most importantly, security, at the frontline of our API operations.
There are some basics I wanted to introduce to my readers when it comes to DNS for their API operations, but I also wanted to shine a light on where the DNS space is headed because of APIs. Some DNS and cloud providers are taking things to the next level, and APIs are central to that. Like most other stops along the API lifecycle, DNS is not just about doing DNS for your APIs, it is also about doing APIs for your DNS. https://goo.gl/E9Pfpb #DataIntegration #ML