Remove Blog Remove Lambda Remove Serverless Remove TDD
article thumbnail

Using Golang for your Serverless projects

Xebia

In one of my previous blogs I wrote why I switched to compiled languages for my lambda functions. But using Golang for your lambda functions does add some challenges. In this blog I would like to share the challenges that I have seen and how to mitigate them. When you are creating a serverless project, this changes.

article thumbnail

Learning Lambda — Part 9

Mike Roberts

Scaling and State This is Part 9 of Learning Lambda, a tutorial series about engineering using AWS Lambda. To be alerted about future installments subscribe to our newsletter , follow Symphonia on twitter @symphoniacloud , and our blog at The Symphonium. Lambda will scale down just as easily as it scales up.

Lambda 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Learning Lambda — Part 9

Mike Roberts

Scaling and State This is Part 9 of Learning Lambda, a tutorial series about engineering using AWS Lambda. To be alerted about future installments subscribe to our newsletter , follow Symphonia on twitter @symphoniacloud , and our blog at The Symphonium. Lambda will scale down just as easily as it scales up.

Lambda 40
article thumbnail

3 Stages of Learning a New Technology

Robots and Pencils

platforms (Linux, AWS Lambda, Google AppEngine etc.) I wouldn’t apply it to: methodologies (TDD, agile, effective writing, etc.) high-level concepts (parsing, ML, IoT, serverless, etc.) I do love a technology that comes with good documentation, but this phase might also include courses, blog posts, or other third party material.

article thumbnail

Three Patterns for an Effective Cloud Native Development Workflow

Daniel Bryant

However, although the initialisation of the infrastructure is fast, it is typically not instantaneous (as you might want, say, in a TDD cycle). TDD for APIs), but also for verifying that a service provides the required functionality and doesn’t regress as the service evolves. This can lead to task/context switching becoming a problem.