The API management space is changing – fast. In the past couple of years alone, we’ve seen huge changes in the deployment patterns that our customers are adopting. In the past, when the use cases were fairly simple, organizations would deploy an API gateway as a SaaS monolith in the cloud, sitting at the edge of the network. They did this because it was the best option available at the time, and the first wave of API management vendors like Apigee had a solution that could support it.

In this article, we will take a high-level look at the differences between an API proxy and an API gateway. When a developer publishes a public API, it’s necessary for that API to have security policies and a way to hide backend logic from API consumers. Decoupling your API from your backend services allows you to shield your apps from backend code changes, and allows users to call your API without worrying about availability.

I’ve just got off a call with one of the largest banks in Sweden, and my brain is racing with ideas. I need to get this down on paper. I want to drop everything I’m doing and spend the next week in that mental headspace where all you do is explore and live and breathe a topic, with occasional breaks for sleep, after which you race out of bed so you can go back to where you left off. You know what I mean. What’s got me so fired up? Climate change.

If you found this article, chances are you already know why you need a solid eCommerce and ERP integration. After all, ERP is kinda of the backbone of any online shop; a master system, if you like, that allows you to effectively handle sales orders and order fulfillments, manage your supply chain and B2B partners, and keep track of the inventory, especially if you sell on multiple channels.

It’s not uncommon for organizations to have to deploy solutions across (or among) multiple security domains. Here, we use the term “security domain” to refer to a segregated network environment, like a restricted internal network or a DMZ. This post will explore some design considerations when deploying Kong Mesh (and Kuma, the CNCF-hosted open source project upon which Kong Mesh is built) in environments with multiple security domains.

In this blog post we are going to cover writing a bare-bones API in ASP.NET that can read, write, and delete data from a test database.

Many companies find that it is not enough to simply keep up with the competition in their industry. Such well-known organizations as Amazon and Microsoft continually expand their service offerings, making it hard to compete. Innovation continues to be a huge buzzword in the software industry. Tech companies need a reliable way to provide clients with what they need most, which is service wherever and whenever they need it. One industry that does this best is the SaaS (Software as a Service) space.

Today, we’re excited to announce the release of Kong Gateway 2.8, which further simplifies API management and improves security for all services across any infrastructure. This announcement demonstrates Kong’s continued commitment to our customers and community by providing a next-generation service connectivity platform to intelligently broker information across modern architectures.

There is no doubt that eCommerce is a staple in the economy post-COVID, which is why omnichannel retail will continue to be a competitive advantage moving forward. Over the past decade, online shopping channels have transitioned from an attractive option to a requirement — but this is just the beginning. You can effectively collect, integrate, and act on customer data through greater business intelligence by implementing digital technologies into your overall retail strategy.