You’ve no doubt heard that IOpipe has been acquired by New Relic (congratulations to both). As part of the acquisition, New Relic has said it intends to retire the IOpipe platform in the next 30 days. If you’re currently relying on the IOpipe platform to monitor and debug your serverless application you have an important decision to make. One option is to try out New Relic’s serverless monitoring functionality.
In this article we’ll introduce the AWS Cloud Development Kit and explore how it can boost the productivity of your development and infrastructure teams. Infrastructure-as-Code is fast emerging as a de-facto standard for development organizations.
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.
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.
Lumigo, the serverless monitoring and troubleshooting platform, today announced that it has achieved Amazon Web Services (AWS) DevOps Competency status. The AWS DevOps Competency status indicates that Lumigo has demonstrated its ability to provide specialized technology that has directly contributed towards its customers’ success. To receive the designation, APN Partners must possess deep AWS expertise and deliver solutions seamlessly on AWS.
The article, Serverless API with ReactJS, was first published on the Serverless Guru website. Let’s build a Serverless REST API for our ReactJS website! In my last article, Deploy ReactJS App with S3 Static Hosting, we discussed hosting a simple React app on AWS with S3. This works great for simple static pages but what if you want to do something more? How do you host your API on S3?
There is a paradox at the heart of serverless. While it’s promoted as a very agile way to develop, a way to push your product as fast as possible to your customers, many development teams find it really difficult to work fast. Why does this happen and can we solve the issue? Let’s start with what makes serverless such a powerful paradigm. Serverless rests on three legs, each of which contributes to the agility that serverless is known for.
AWS Lambda has gained good traction for building applications on AWS. But, is it really the best fit for all use cases? Since its introduction in 2014, Lambda has seen enthusiastic adoption – by startups and enterprises alike. There is no doubt that it marks a significant evolution in cloud computing, leveraging the possibilities of the cloud to offer distinct advantages over a more traditional model such as EC2.
