Running Your Own Rendering Infrastructure

Running Your Own Rendering Infrastructure

In addition to hosting the popular OSM-base Toner, Watercolor, and Terrain tile sets, Stamen incorporates custom cartography into much of our client work. This is a behind-the-scenes walkthrough covering the evolution of our rendering infrastructure and the peripheral services that help to make our work unique.

A0b49382b6dcd9dd4602c3088717724e?s=128

Seth Fitzsimmons

April 13, 2014
Tweet

Transcript

  1. Running Your Own Rendering Infrastructure Seth Fitzsimmons Stamen Design http://flic.kr/p/8sJotc

  2. Golden Gate National Parks Conservatory

  3. Lessons Learned • Easy deployment is key to effective design

    iteration • Shield what’s likely to break • Repeat
  4. services vs. a Service

  5. Goals • minimal administrative overhead • straightforward to update data

    and styles • cost-effective • performant • flexible • can be handed over to clients with minimal technical capacity • horizontally scalable
  6. Concerns, Separated Ephemeral Caching Cache Seeding Persistent Caching Rendering +

    Post-Processing Data
  7. The Cloud? http://flic.kr/p/yqcg

  8. Concerns, Separated Ephemeral Caching Cache Seeding Persistent Caching Rendering +

    Post-Processing Data
  9. Ephemeral Caching http://flic.kr/p/5RjK9i

  10. Cache Seeding http://flic.kr/p/PV6hG

  11. Persistent Caching http://flic.kr/p/joAi8B

  12. Rendering + Post-Processing http://flic.kr/p/6yqYZv

  13. Data http://flic.kr/p/4CL7a7

  14. tl;dpa • Easy deployment is key to effective design iteration

    • Shield what’s likely to break • Repeat • Fastly • AWS / Heroku • github.com/mojodna/tessera • github.com/mojodna/tp
  15. Thank you! ! github.com/mojodna github.com/stamen github.com/parks-conservancy ! seth@stamen.com