🎂 Make a wish and blow out the candles…we’re celebrating Kong’s sixth anniversary! 👏👏👏 In 2015, Mashape open sourced Kong Gateway, launching the next generation of API management. In our last anniversary post, I took a look back at our history. For this 6th anniversary post, I’ll focus on how this year went and look forward to what’s coming up next.
President Joe Biden issued an “Executive Order on Improving the Nation’s Cybersecurity” as of May 12, 2021. The order includes numerous actions and mandates to confront the dangers of cyber attacks that are increasing in frequency and sophistication. Cybersecurity has real and significant implications, both in economical and national security terms. At the time of this writing, the Colonial Pipeline cyber attack caused quite a stir on the USA’s east coast.
In our second Kong and Okta tutorial, we’ll go through the authorization code flow applied to user authentication processes. This series will show you how to implement service authentication and authorization for Kong Konnect and Okta using the OpenID Connect (OIDC) plugin.
As we've discussed in our previous Service Discovery post, decoupled services in a microservice architecture communicate via APIs. But what about the communication between clients outside of your system and the services within your application? How does that communication work? An API gateway is a powerful component in a microservice architecture. Pairing its functionality with a serverless platform like Koyeb saves engineering teams time and maximizes computing resources efficiency.
If you’ve not heard of decK (our declarative configuration and drift detection tool for Kong Gateway) before, now’s a great time to get hands-on with it as we’ve just shipped decK v1.7.0 with a whole host of new goodies. Oh, and it’s all open source as usual.