Readers turned to SHRM Online this year for articles about how HR operates around the world—especially about how HR is preparing for a new data protection law in Europe. https://goo.gl/1K79WA #GlobalHR #HRTech
An API-First Approach for Microservices on Kubernetes
This article is featured in the new DZone Guide to Microservices. Get your free copy for more insightful articles, industry statistics, and more!
Moving to containerized microservices is not an easy transition for developers who have been building applications using more traditional methods. There are a lot of new concepts and details developers need to consider and become familiar with when they design a distributed application, which is what a microservice application is. Throw Docker and Kubernetesinto the mix and it becomes clear why many developers struggle to adapt to this new world.Developers want to focus on the development of the logic, not on the code necessary to handle the execution environment where the microservice will be deployed. APIs have always been a productive way to connect services, and this is still true for microservices on Kubernetes (K8s). In this article, we will lay out why you can benefit from an API-first approach for building microservices applications on Kubernetes. Before we can dive into the how, let’s have a quick review of what API-first means and what one commonly refers to services in K8s. https://goo.gl/JqVvLA #DataIntegration #ML
Build a REST Web Service Using Spring
ICYDK: This tutorial provides a step-by-step guide for building a REST web service using the Spring framework.
Prerequisites: https://goo.gl/6MnwGM #DataIntegration #ML
The Shifting API Landscape
ICYMI: I’ve been watching, and trying to move forward the API conversation across all business sectors for seven years now. I’m not a startup. I’m not an API service provider. I’m not steering an enterprise group. I’m not an investor. I’m a software architect and storyteller who saw the potential for leveraging web infrastructure to deliver data, content, media, and algorithms across the web, to our mobile phones, as well as the seemingly endless number of devices we are connecting to the Internet in our personal, professional, and industrial worlds. I’m not studying the landscape so I sell to it. I am studying the landscape so I can understand it. While most of my readers will not grasp that difference, it gives me a fundamentally different view of what is going on across the space.
In the last seven years I’ve had a focus on helping individuals at SMB, SME, enterprise, organizations, institutions, and government agencies understand what APIs are, and why they should be doing them. In 2017, I feel that mission becoming irrelevant based upon the shifting API landscape. As I work on my third API-first strategy for a top level federal agency in response to an RFI in recent months, prepare for an all week API workshop at Mutual of Omaha in Nebraska, and bookmark the job postings for API architect at almost every major bank in the US and UK, my cute little mission to help understand people understand what APIs are clearly needs to be retired. While there are plenty of people who still need to be educated what APIs are, and that they should be doing them, I’m going to leave it to the waves of other pundits, advocates, evangelists, and analysts to help onboard them. I’ve done my time. https://goo.gl/hjP463 #DataIntegration #ML