An HTTP request's journey through a platform-as-a-service
Formal Metadata
| Title | An HTTP request's journey through a platform-as-a-service |
|
| Title of Series | |
| Part Number | 21 |
| Number of Parts | 119 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Berlin |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Giles Thomas - An HTTP request's journey through a platform-as-a-service
PythonAnywhere hosts tens of thousands of Python web applications, with traffic ranging from a couple of hits a week to dozens of hits a second. Hosting this many sites reliably at a reasonable cost requires a well-designed infrastructure, but it uses the same standard components as many other Python-based websites. We've built our stack on GNU/Linux, nginx, uWSGI, Redis, and Lua -- all managed with Python. In this talk we'll give a high-level overview of how it all works, by tracing how a request goes from the browser to the Python application and its response goes back again. As well as showing how a fairly large deployment works, we'll give tips on scaling and share a few insights that may help people running smaller sites discover how they can speed things up. |
|
| Keywords | |