AWS Lambda has been around for a few years now, and it remains the most popular way to experiment with serverless technology. If you're not familiar with serverless, it's a model of development in which managing, provisioning, and scaling servers is abstracted away from application development. Servers do exist in a serverless world, but they are completely managed by the cloud provider, allowing developers to focus on packaging their code for deployment.

While writing a comparison of Kubernetes and Koyeb, we tried to determine how much operating a Kubernetes cluster really costs. This section of our comparison took us hours to write and ended up being so long that we decided to write a dedicated post about it. Full disclaimer: At Koyeb, we're building a serverless platform and we have a purpose-built orchestration engine.

AWS Lambda lets you run your code without worrying about the nuts and bolts of server management or scaling. You might even say it's "serverless." In this article, Jeffrey Morhous shows us how to get started writing Lambda functions in Ruby.

Serverless Java applications use modern cloud computing to let developers focus on business logic rather than infrastructure. In a serverless environment, the infrastructure provider takes care of scaling, runtimes, resource management, security and other specifics. Concerns such as number of instances to run and which OS to use are managed by Function as a Service (FaaS) platforms, allowing developers to focus on application code.

Google's Cloud Functions let developers run their code in production in a scalable way without worrying about the minutiae of server administration. In this article, Subomi shows walks us through building a real-world service using GCF.

Here at Koyeb, 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?".

Hello again! Welcome to Part 2 of this article series where we go through database-driven architectures by understanding the nitty gritties of a chat app where you can edit messages. Here's the Part 1 of this article series, if you missed it: Database-driven realtime architectures: building a serverless and editable chat app - Part 1 Check out the editable chat app or explore the project on GitHub.

Database-driven realtime architectures are becoming more and more common as evidenced by key backers and widespread use of software like Firebase and Supabase. The two key priorities for an app following database-driven realtime messaging are long-term storage and change data capture (CDC) updates from the database. In this two part article series, we’ll take a detailed look at a fully serverless chat app where you can edit previously published messages.

Today's users of web and mobile applications and services expect fast and outstanding experiences. Delivering successful web services and applications means meeting these baseline expectations: In this blog post, we dive into why these three goals are vital to modern web applications and services. Then, we will look at how building global and distributed architectures achieve these goals.