Functions and Containers Lambda layers Let functions easily share code; upload layer once, reference within any function Layer can be anything: Dependencies, training data, configuration files, etc. Promote business logic Built-in support for secure sharing by ecosystem Including library dependencies in a layer Runtime Folders Python python python/lib/python3.7/site-packages (site directories) Node.js nodejs/node_modules Lambda Layer • 99.95% SLA Decouple and Modularize your Serverless Application Lambda layers • Let functions easily share code; upload layer once, reference within any function • Layer can be

. . . . . . . . . . . . 1 1.3 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.4 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 Forms . . . . . . . . . . . How to write reusable apps | Writing your first patch for Django 1.3 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application

I can’t stand your template language. Do I have to use it? Do I have to use your model/database layer? How do I use image and file fields? How do I make a variable available to all my templates? FAQ: Tutorials: How to write reusable apps | Writing your first patch for Django The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application databases | Providing initial data | Optimize database access | PostgreSQL specific features The view layer Django has the concept of “views” to encapsulate the logic responsible for processing a user’s request

. . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.7 Forms . . . . . . . . . . . How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application

I can’t stand your template language. Do I have to use it? Do I have to use your model/database layer? How do I use image and file fields? How do I make a variable available to all my templates? FAQ: Tutorials: How to write reusable apps | Writing your first patch for Django The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application databases | Providing initial data | Optimize database access | PostgreSQL specific features The view layer Django has the concept of “views” to encapsulate the logic responsible for processing a user’s request

. . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.7 Forms . . . . . . . . . . . How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application

. . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.7 Forms . . . . . . . . . . . How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application

I can’t stand your template language. Do I have to use it? Do I have to use your model/database layer? How do I use image and file fields? How do I make a variable available to all my templates? FAQ: Tutorials: How to write reusable apps | Writing your first patch for Django The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application databases | Providing initial data | Optimize database access | PostgreSQL specific features The view layer Django has the concept of “views” to encapsulate the logic responsible for processing a user’s request

I can’t stand your template language. Do I have to use it? Do I have to use your model/database layer? How do I use image and file fields? How do I make a variable available to all my templates? FAQ: Tutorials: How to write reusable apps | Writing your first patch for Django The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application databases | Providing initial data | Optimize database access | PostgreSQL specific features The view layer Django has the concept of “views” to encapsulate the logic responsible for processing a user’s request

. . . . . . . . . . . . 2 1.4 The model layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 The view layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.6 The template layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.7 Forms . . . . . . . . . . . How to write reusable apps | Writing your first patch for Django 1.4 The model layer Django provides an abstraction layer (the “models”) for structuring and manipulating the data of your Web application