Luke
☁️ Cloud Native 🌈 DevOps ⚡️ Serverless ⌨️ Node.js
In this talk, Luke will describe the design, build and operation of a cross-domain event distribution service at The LEGO Group. The cross-domain event service is part of a production workload powering global e-commerce at massive scale, running on the AWS public cloud. A novel approach to standardising event schema and payloads that utilises AsyncAPI and CloudEvents will be presented. We will also explore the use of web standards in cross-domain event production, such as JSON Patch for data marshaling and JSON Web Tokens for encoding and encryption of payloads. We'll explore how the use of AsyncAPI tools supports the delivery lifecycle of this system, including Modelina for automated generation of type definitions and Generator for documentation. We will also see how AsyncAPI schema can be integrated with Spotify’s Backstage platform to simplify the onboarding of new event consumers through event documentation and discovery.
The LEGO Group was a super early adopter of the serverless mindset and associated technology. It is time to review how one of its core products continues to operate and innovate 3 years on. We will take a look at the serverless, event-driven architecture powering The LEGO Group's payments platform, Brickbank, and how it facilitates e-commerce on a global scale. We'll explore the full software delivery lifecycle of the payments platform, including development, testing, release and observability. We will look at some of the key AWS services that play crucial roles in the platform's architecture, including Lambda, Step Functions, DynamoDB, EventBridge, CDK and Macie. We will also assess how a mature serverless application remains up-to-date with constantly evolving best practices, industry trends and feature requests.
The LEGO Group was a super early adopter of the serverless mindset and associated technology. It is time to review how one of its core products continues to operate and innovate 3 years on. We will take a look at the serverless, event-driven architecture powering The LEGO Group's payments platform, Brickbank, and how it facilitates e-commerce on a global scale. We'll explore the full software delivery lifecycle of the payments platform, including development, testing, release and observability. We will look at some of the key AWS services that play crucial roles in the platform's architecture, including Lambda, Step Functions, DynamoDB, EventBridge, CDK and Macie. We will also assess how a mature serverless application remains up-to-date with constantly evolving best practices, industry trends and feature requests.
In this talk, Luke will walk-through how to write the most awesome Node.js Lambda functions, from project initialization through to operation. We'll look at how AWS Lambda functions work and why this matters. We'll then explore the best practice for folder structure, code standards, static analysis, testing, security and monitoring. All by employing the latest and greatest standards, as used by serverless experts!
Unleash the full power of serverless by shipping your software on day 1 - and every day after that! Let's look at how we can snap together a small set of tools to quickly and simply get your serverless application running in the AWS cloud. Featuring: VS Code, GitHub and AWS. We will explore the basics of local development, infrastructure as code, automated tests, continuous delivery pipelines and observability!
Serverless engineering has a reputation for being slow and cumbersome. There is a better way. Let's explore how to combine tools like SST with continuous delivery workflows to get serverless engineers shipping code from keyboard to production on day 1, and every day after.
Using Amazon Macie to build serverless data pipelines for detecting sensitive data leaks
Workshop exploring event-driven architecture, using Amazon EventBridge and AWS Step Functions.
A quick tour of how we are using Serverless at Cancer Research UK
A quick tour of how we are using Serverless at Cancer Research UK
A quick tour of how we are using Serverless at Cancer Research UK
It's 2020. Node.js is 10 years old. What do the next 10 years look like for the JavaScript runtime environment? Let's find out!