Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Using a custom template loader at scale

Dane Hillard
September 23, 2019

Using a custom template loader at scale

In the interest of team autonomy and fault tolerance, we partition parts of our platform into isolated Django projects. Although this allows for independent development work, it also means that some resources that are traditionally created on a per-project basis, like globally-used templates, need to be shared across projects. A reusable Django app could normally do the trick, but we want to deliver template updates to all consumers as instantaneously as possible without deployments. How do we do it?

Dane Hillard

September 23, 2019
Tweet

More Decks by Dane Hillard

Other Decks in Technology

Transcript

  1. @easyaspython Django approach • Distinct Django projects ◦ For fault

    tolerance ◦ For independent performance profiling • A shared core of apps and packages ◦ Authentication ◦ Permissions ◦ Search form ◦ Look and feel 13
  2. @easyaspython Desires • Consumers receive updates without deployment • In

    near-real time • Without affecting page load performance 17
  3. @easyaspython Custom template loader 20 • What is it? •

    How do we use it? • What did it get us? • What’s left?
  4. @easyaspython Desires • ✅ Consumers receive updates without deployment •

    ✅ In near-real time • ✅ Without affecting page load performance 32