veyepar: From Hobby to Planet Scale: 5 Different Ways to Deploy Python

Author(s):	Mike Van Winkle
Location	Reis River Ranch
Date	apr Sun 27	Days Raw Files
Start	13:10	First Raw Start	12:58
Duration	00:25:00	Offset	0:11:15
End	13:35	Last Raw End	13:58
Chapters	00:00 0:13:19
Total cuts_time	34 min.

https://pretalx.northbaypython.org/nbpy-2025/talk/ZSMCNT
raw-playlist raw-mp4-playlist encoded-files-playlist host mp4 svg png

assets release.pdf From_Hobby_to_Planet_Scale_5_Different_Ways_to_Deploy_Python.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

You're finally done building your super awesome world-changing python project and now you want to get it out there. Where do you start? DIY? Premium Services? In this talk I will cover 5 different ways to deploy Python and when you should use them. Whether you have a small hobby site that you want to deploy on the cheap, or have a big project you expect to scale, we will discuss all the things you need to consider when deploying Python. I will present a matrix of decision vectors (complexity, reliability, scale, cost, fun) and how each approach stacks up and examples and references of each.

The approaches included in this talk will be:

Self-managed (self-hosted) VPS using native ubuntu –  This approach is best suited for hobby sized or small to medium projects where the primary deciding factor is either cost or learning.

Self-managed VPS hosting with Docker – This approach is also suitable for small projects but having to install and manage docker containers introduces additional complexity, though that complexity may be useful once you need to scale.

Serverless using AWS Lambda – This approach can be cost effective for small to medium projects, but the complexity may not be worth it for hobby sized projects.

Serverless using Kubernetes – This is a very complex approach but is likely the best way to affordably scale to planet scale.

Premium services like Vercel or Render –  This approach is great for some projects but not for all. I will cover the when and when not to consider using premium services.

Comment:

production notes