aws lambda

AWS LAMBDA

Richard GlewCTO

Tim FairbrotherSenior Developer

Or Instances…

Or Containers…

Or Containers…

*No whales were harmed in the making of this slide

INTRODUCING AWS LAMBDA

▸ A compute service that runs your code in response to events and automatically manages the underlying compute resources for you.

▸ Allows you to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

▸ Runs your code on high-availability compute infrastructure and performs all the administration of the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, code and security patch deployment, and code monitoring and logging. All you need to do is supply the code.

NOT BAD

LANGUAGES

• Native support for NodeJS, Python & Java 8

• Can spawn any other process that runs on Amazon Linux - almost all languages

BENEFITS• Price

• No management of infrastructure

• Less DevOps skills needed

• Massive scalability

• Quick to deploy

• Not locked to AWS

THINGS TO BE AWARE OF…• Not in ap-southeast-2 (Sydney) just

yet…

• Tends to be used in conjunction with other AWS services

• Dev workflow…

• Architecture will be more complex than a small monolithic app

• Still early days for many use cases, lots of roll-your-own at the moment. Eg: end to end testing, monitoring

DEMO

DEMO CODE

• https://github.com/intrepica/lambda-core

SUMMARY

• Can be used now

• Expect to see it improve a lot over time

• People are working on this right now. See the JAWS project.

• Is a big deal.

THANKS!