Systems | Development | Analytics | API | Testing

Imagine the following hypothetical scenario: in a rental property management system, Employee A starts editing contact info for Rental X, adding some extra phone numbers. Around the same time, Employee B notices a typo in the contact info for exactly that Rental X and performs an update. A couple of minutes later, Employee A updates Rental X’s contact info with the new phone numbers, and … the update fixing the typo is now gone! That’s definitely not great!

These days, a lot of companies are moving towards cloud native applications and declarative configurations. This is also true for the traditional API gateways (e.g., MuleSoft, Axway, etc). Customers are looking for new technologies which fit better in their cloud environments and also are faster and cheaper. The main challenge here is how to migrate the existing APIs to the new platform.

We're kind of crazy about providing the fastest way to deploy applications globally. As you might already know, we're building a serverless platform exactly for this purpose. We recently wrote about how the Koyeb Serverless Engine runs microVMs to host your Services but we skipped a big subject: Global Networking. Global Networking is a big way of saying "How are my requests processed?". A short answer is: requests go through our edge network before reaching your services hosted on our core locations.

In this episode of Kongcast, I had the pleasure of speaking with Viktor Farcic, developer advocate at Upbound, about why empowering developers to manage the full application lifecycle helps app development teams increase efficiency.

In this three-part blog series, we examine the critical role Kubernetes plays in shaping the future of infrastructure, including the rise of containers and Kubernetes. The first in the series covers Next-Generation Application Development. The second covers the Next Frontier: Container Orchestration. And the third covers How Kubernetes Gets Work Done.