In our last blog post, we discussed the evolution of APIs from early computing to the PC era. In this post, we’ll discuss the evolution of APIs in the early internet age. Along the way, we’ll touch upon associated core technologies such as eXtensible Markup Language (XML) and discuss the introduction of web services and its common components: SOAP and WSDL.
As organizations look to accelerate their digital transformation initiatives, a couple of key trends are prevalent. First, there is a movement from monolithic to smaller cloud native microservices. Second, there is more pressure to innovate, resulting in an explosion of APIs and connections to secure. To help organizations address these trends, Kong is joining forces with Okta to deliver the best-in-class identity for API management.
SOAP (Simple Object Access Protocol) Web Services have been around for a long time, and not too long ago was the default when it came to exposing functionality using a common format. SOAP is a standards-based web services access protocol that relies on XML to describe the web service and for all request and response messages.
We love abstractions. We want to make things easier for developers, teams and end users. In doing that, sometimes we build things a little bit too complex for those who don’t already understand the pain points for which the abstraction layers were built. Kubernetes is an example of this; it solves a very real, very painful problem, but it is notoriously difficult to wrap your head around.
To work and live in today’s digital world, we are unquestionably dependent on interconnected applications. These applications might be massive and highly complex, but they’re also constructed from reusable building blocks, which we call an Application Programming Interface—the API. API adoption is on the rise across all industries. However, APIs aren’t new. They came about from the natural evolution of writing computer software.
After you’ve built your microservices-backed application, it’s time to deploy and connect them. Luckily, there are many cloud providers to choose from, and you can even mix and match. Many organizations, like Australia Post, are taking the mix-and-match approach, embracing a multi-cloud architecture. The microservices that make up a system no longer have to stay on a single cloud.
In this episode of Kongcast, I had the pleasure of speaking with Aaron Weikle, the founder and CEO at MS3, about supporting legacy-based applications as companies add the next generation of microservices. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.
A developer portal is a storefront to your APIs (the products) that internal and external developers are trying to consume. The Kong Developer Portal provides a single source of truth for all developers to locate, access and consume services. With intuitive content management for documentation, streamlined developer onboarding and role-based access controls (RBAC), Kong’s Developer Portal provides a comprehensive solution for creating a unified developer experience.
This post highlights how you could use Kong Gateway to implement a solution for the Australian Consumer Data Standards (CDS), which is part of the Consumer Data Right legislation introduced by the Australian Government in November 2017. As detailed on the Australian ACCC website: CDR will give consumers greater access to and control over their data and will improve consumers’ ability to compare and switch between products and services.
Many organizations have been able to accomplish impressive things using Kong products, including Kong Konnect, Kong Enterprise, Kong Gateway, Kuma and Insomnia. We recently honored four of these enterprises in the inaugural Cloud Connectivity Innovator Awards program during Kong Summit 2021.
