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

NU.nl performance and our journey in the Django realm

Besma
February 24, 2016

NU.nl performance and our journey in the Django realm

These are the slides of my talk at the Django meetup hosted by Byte

Besma

February 24, 2016
Tweet

Other Decks in Programming

Transcript

  1. [email protected] Our platforms • Web – Desktop and mobile •

    Mobile – tablets, phones and smart watches
  2. [email protected] Development process • DeVops mind set team • Tools

    – Development: Jira, Bamboo, Hipchat – Monitoring: GA, New Relic
  3. [email protected] Our output as Web/API team • Serving static pages

    • Serve Push Notification for big news • Serve the raw data
  4. [email protected] Microservices • Projects that serve a single purpose •

    Together projects create a microsystem that fits within the Sanoma ecosystem
  5. [email protected] Past ecosystem • The entire stack used to be

    written in php • Development and maintenance by external party
  6. [email protected] Current ecosystem • Most of the stack in Django

    • Development and maintenance by our team
  7. [email protected] Near future ecosystem • All of the stack in

    Django • Development and maintenance by our team
  8. [email protected] Block structure • Business and editors decide on the

    layout • Editors supply the blocks with content • Layout is served to FE and mobile
  9. [email protected] How do we deal with these challenges in general?

    • Django security solutions • DRF as dataprovider • Caching • Rigorous testing
  10. [email protected] How? Webservers • Software updated and servers rebooted •

    Updated nu.nl stack to python 2.7 • Updated nu.nl stack from Apache to nginx • Disabled django.views.static.serve • Used Serpy as serializer
  11. [email protected] Other performance challenges • Pages are no longer static

    • API: serving blocks instead of layouts to mobile applications