As a team that does pure serverless, we place a lot of emphasis on fast deployments. Lately, though, as our codebase has gotten larger, and the number of interactions between the microservices has increased, we have come up against the classic problem of excessively long test execution times in our serverless continuous integration.
Unit tests and integration tests are vitally important, but sometimes even those aren’t sufficient to ensure that critical services in your application will function smoothly in production. In those cases, adding a staging step to our CI/CD process allows us to test a feature with real data in a less supervised environment. For example, here at Lumigo we decided to use it for our Node.js tracer.
As you read this, API Gateway HTTP API is now Generally Available. This is an important milestone, and kudos to the AWS API Gateway team for turning this around so quickly. As part of the GA announcement, they also introduced a number of features, including...
To round out our series on the serverless open source community, Itay Herskovits, CTO of Funzing.com – a community marketplace for local experiences – picks 10 must-have Serverless Framework plugins. As serverless technology has evolved, a few early-movers have become staples of serverless development. One of these is Serverless Framework, an extensible serverless application management tool that helps you maintain, support, and deploy your serverless code.
SNS and SQS have been the goto options for AWS developers when it comes to service integration. However, since its (much needed!) rebranding, EventBridge (formerly CloudWatch Events) has become a popular alternative. If you’re still on the fence, then allow me to give you 5 reasons why you should consider using EventBridge instead of SNS.
Next in our series on the Amazon Builders’ Library, Lumigo Director of Engineering – and newly-minted Serverless Hero – Efi Merdler-Kravitz picks out the key insights from the article, Instrumenting distributed systems for operational visibility, by AWS Principal Engineer (AWS Lambda), David Yanacek.
Serverless applications, due to their distributed nature, are often stuck having to reinvent the wheel. While small utility scripts and functions are often easily instrumented and monitored, anything of a transactional nature will need to implement special code to provide developers with common tools like stack traces, atomicity, and other patterns that rely on a singular flow of control.
Next in our series on the Amazon Builders’ Library, Mike Roberts of Symphonia picks out the key insights from the article Going faster with Continuous Delivery by AWS senior manager of software development Mark Mansour.
The infrastructure that runs your applications can be nearly as complex as the applications it supports. This complexity generally scales with the resilience of the architecture of your application, the scaling needs, and any security concerns. Thus, successful infrastructure for traditional applications often relies on a comprehensive tooling suite that allows the infrastructure engineers to iterate upon and improve your application’s resources.
In our latest article on the Amazon Builders’ Library, Yan Cui highlights the main takeaways from the article, Implementing health checks, by AWS Principal Engineer David Yanacek.
