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.

For the DevOps-averse developer, lambdas are heaven. They can focus on writing self-contained and modularized pieces of code, deploying these functions for on-demand execution without being concerned about resource management or infrastructure. Lambda execution , however, can be tricky. Serverless security with the AWS API Gateway can feel daunting, especially when all you want to do is call a simple function as an API endpoint. For this, there’s the ease of Kong Gateway .

Whether you're implementing a microservice architecture that will be scalable and resilient or forward-thinking for interoperability possibilities, APIs provide the essential level of abstraction that enables communication between separate pieces of software. Modifying an API architecture once it is live is no small feat, so taking the time before building one to identify your needs and goals for your API is a worthwhile step that will help you create the API you want.

Lambda is an excellent option for deploying lower-traffic web services when you don't want to maintain another server and you want easy access to all of AWS's other services. In this article, Godwin Ekuma shows us step-by-step how to deploy our Rails apps to AWS Lambda.