veyepar: Running Vintage Software: PyPI's Aging Codebase.

Author(s):	Ernest W. Durbin III
Location	Mystic Theatre
Date	dec Sun 03	Days Raw Files
Start	17:25	First Raw Start	16:59
Duration	0:25:0	Offset	0:25:05
End	17:50	Last Raw End	17:59
Chapters	00:00 0:04:17
Total cuts_time	28 min.

https://2017.northbaypython.org/schedule/presentation/5/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Running_Vintage_Software_PyPIs_Aging_Codebase_2.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

From it's origins in the early days as a metadata server to the current trove of hosted packages, PyPI has grown into a critical part of the Python Communities Infrastructure.

Originally conceived and implemented in 2002 as a simple set of metadata, the codebase that backs PyPI has been pushed well beyond it's limits. While some may call it "legacy" software, I choose to view it like one may view a classic car that still sees it's time on the road.

This talk will present some of the challenges common to keeping a Vintage Car on the road as well as their counter parts when dealing with Vintage Software and take a look at the approaches that have worked well to keep PyPI up and running as a full rewrite is underway.

Also covered will be an overview of the history of PyPI as a whole, as well as what the future holds and how you (yes you!) can contribute.

Technical Topics covered include:

- External caching, Content Delivery Networks
- Internal caching, to speed up common or repetitive requests which just can't be cached in the CDN
- Metrics, Metrics, Metrics! Not just for monitoring! Keep track of what features just aren't worth supporting any longer or what methods are prime for optimization
- Dealing with issues related to scaling even when major refactors or changes aren't feasible.
- Increasing reliability

The desired outcome for attendees of this talk is a sense of how to approach a Vintage codebase that must remain up and running even as it's predecessor may be in progress. Big rewrites can take time! Don't feel defeated sustaining an old project, it is what your users need!

Novice attendees may find the history and high level concepts interesting, but Intermediate attendees should get the most out of this talk. Specifically some of the technical bits will make the most sense and be most applicable if you've ever worked on a medium to large production web service.

Comment:

production notes