Over the last decade, DevOps has become an important part of software engineering culture, influenced by the wide adoption of microservices, containers and cloud computing. A recent step in the evolution of cloud-based and microservice architecture is the serverless computing – a code execution model where the cloud provider takes total responsibility for the operating system and hardware management.

Serverless Hero Yan Cui explains when and why you should use API Gateway service proxies, and introduces an open source tool to make it easy to implement. One of the very powerful and yet often under-utilized features of API Gateway is its ability to integrate directly with other AWS services. For example, you can connect API Gateway directly to an SNS topic without needing a Lambda function in the middle. Or to S3, or any number of AWS services.

When you look at an X-Ray trace for a Lambda cold start, you will see an Initialization subsegment. This subsegment represents “the function’s initialization code that is run before the handler”. This is where the runtime would resolve any dependencies, or initialize global variables. These are executed only once, so they don’t have to run on every invocation. The more dependencies you have, the longer this initialization step takes.

In new and quickly-expanding fields like serverless, long-standing experts are few and far between. I am excited to welcome Tim Wagner, the original leader of the serverless movement, to the Stackery Board of Directors. Tim spent six years at Amazon Web Services as the General Manager of AWS Lambda, where he oversaw the team that built the success of serverless as a platform. In many ways, we have them to thank for creating the environment that supports Stackery and the serverless ecosystem.

Here at Lumigo, we are big fans of serverless. And a big part of working with AWS Lambda involves using many other AWS services. For example, services such as SNS and SQS are often used to chain Lambda functions together. They are essential ingredients of an event-driven architecture, where systems are loosely coupled through events. However, they also pose a challenge to how we test our systems and how to get fast feedback on what’s happening in the system.

AWS introduced the Serverless Application Model (SAM) to ease the building of serverless applications on AWS. Essentially, it is an extension of AWS CloudFormation, and consists of two major components: SAM template specifications and SAM CLI. In this article, we’re going to share five tips to get the most out of AWS SAM templates. So, without further ado, let’s dive right in.

I’ve spent a lot of time with the development community over the years but every time I get to talk to people in the serverless community I’m constantly surprised by the passion and the general excitement over this technology. Below is one of the latest of said topics and I wanted to share it with you.

Stackery has launched a partner program currently centered around Systems Integrators. Here’s why.