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.
There are good reasons for spreading workloads and applications across multiple clouds. Options include using a combination of public and on-premises cloud platforms, a strategy known as hybrid cloud—or using more than one public cloud provider, a strategy known as multi-cloud. What are those benefits? And what are some of the best strategies for achieving them? Let’s explore that.
Changing the technology an organization works with is a bit like taking up a new sport. Your initial excitement leads you to buy the most expensive equipment you can find, leaving you soon to realize that your new tools have created a steep learning curve. Transitioning out of monolithic applications to microservices is quite similar.
Have you ever found yourself in a situation where all your service mesh services are running in Kubernetes, and now you need to expose them to the outside world securely and reliably? Ingress management is essential for your configuration and operations when exposing services outside of a cluster. You need to take care of the authentication, observability, encryption and integration with other third-party vendors alongside other policies.
