In this first section, I’ll provide a quick overview of the business case and the tools you can use to create a Kubernetes ingress API gateway. If you’re already familiar, you could skip ahead to the tutorial section. Digital transformation has led to a high velocity of data moving through APIs to applications and devices. Companies with legacy infrastructures are experiencing inconsistencies, failures and increased costs. And most importantly, dissatisfied customers.
After working with a diverse set of software engineering teams, we at Moesif have gained a unique perspective on what traits enable engineers to take on leadership positions and become outstanding managers vs others who have a harder time rising through the ranks. Gaining an advanced title and responsibility is not an easy task. After all, there are far more software engineers than executives at a company regardless of size. So how do you stand out to land that awesome VP or C-suite role?
This blog post is part two of a three-part series on how we’ve scaled our API management with Kong Gateway, the world’s most popular open source API gateway. We understand that this post’s title may seem a little controversial. When we announced that our new API gateway solution might be an open source product, we got many questions from voices across the company.
As you build and maintain more applications, your authentication strategy becomes increasingly important. It may also be top of mind for your boss since technology leaders cited “improve application security” as one of their top priorities in this year’s Digital Innovation Benchmark. The Kong Gateway JWT plugin is one strategy for API gateway authentication. JWT simplifies authentication setup, allowing you to focus more on coding and less on security.