Ben Kehoe wrote a post about AWS API Gateway to Lambda integration: How you should — and should not — use API Gateway proxy integration with Lambda. In his post, Ben gave a few reasons why he believes using API Gateway Proxy Integration is an anti-pattern. Ben does a great job summarizing how the integration works. He writes: The pattern that I am recommending against is the “API Gateway proxy integration” as shown in the API Gateway documentation here.

We are going to talk about an essential part of AWS Lambda called “AWS Step Functions.” What are Step Functions? Why are they important for AWS Lambda users? What are they used for, and what can we expect to get by using them? Bare with us, and discover more critical information on Step Functions throughout this article. We’ll begin with the explanation of what are Step Functions. AWS Step Functions service is the most recent service released by none other than Amazon Web Services.

If you’re in developing business, you’ve probably heard about AWS Lambda by now. In case you haven’t, AWS Lambda has been among us for years, and it certainly brought a whole new level for running a code. The benefits of using AWS Lambda are vast, and many developers already use AWS Lambda daily. If you’re not among them, read through this article to learn more about what AWS Lambda can do for you and your code.

In 2018, AWS pulled in $25.7 billion. Amazons serverless cloud-computing platform keeps growing every year, and with that growth comes the same types of problems every massive effort faces: the limits and deterioration of performance as time goes on. With the rise of serverless technology, developing application and new services has never been easier.

Serverless applications require a whole new approach to development workflow. In this article, Lumigo Director of Engineering Efi Merdler-Kravitz details the guiding principles and tools used at a 100% serverless company to ensure the most efficient workflow possible. We are not going to talk about product development flow (no product managers were harmed during the making of this post!).

As a company providing tooling to enable developers and operations teams to adopt a productive serverless workflow, Stackery is closely integrated with Amazon Web Services (AWS). Our customers are development teams who want to confidently build on AWS serverless and then manage the pipeline to production with confidence that what gets built and changed is done efficiently and well.

A big part of Checkly runs on AWS Lambda, but I never really discussed it in depth before on this blog. So here we go. Topics are: Note, I'm using "Lambda" here as a stand in for "serverless" in general. Many of the things discussed here apply to either Google Cloud Functions, Azure Functions and possibly Zeit although I've never used it. First something on how we use Lambda. Last week we went over 35 million check runs.

AWS Lambda is a service that confuses many people. For that reason, you may be wondering just how it works, and how you’d use it to build a highly scalable event-driven application. As someone who’s presumably no stranger to the internet, you must have seen the terms serverless, function-as-a-service, or AWS Lambda thrown across your screen a few times. Perhaps you’re looking to learn more. If so, you’re in luck.

This post takes a look at Kotlin, a relatively new programming language that runs on the JVM, and explores how it can be used to build serverless web apps on AWS using Lambda and API Gateway. In programming language terms Kotlin is a relative newcomer. It was first announced in 2011 by JetBrains, the makers of IntelliJ IDEA, and was designed as a modern successor to Java.