Varnish: where developers & sysadmins meet - Varnish Summit Amsterdam 2015

Ca901ddcea38854b9783781c91fc87c9?s=47 Thijs Feryn
November 05, 2015

Varnish: where developers & sysadmins meet - Varnish Summit Amsterdam 2015

Varnish: where developers & sysadmins meet - Varnish Summit Amsterdam 2015

Ca901ddcea38854b9783781c91fc87c9?s=128

Thijs Feryn

November 05, 2015
Tweet

Transcript

  1. Where developers & sysadmins meet By Thijs Feryn Varnish

  2. Hi, I’m Thijs

  3. I’m @ThijsFeryn on Twitter

  4. I’m an Evangelist At

  5. I’m an at Evangelist

  6. I’m a at board member

  7. Early days

  8. Down

  9. Website performance?

  10. More servers

  11. Identify slowest part

  12. Optimize database

  13. Optimize runtime

  14. After a while you hit the limits

  15. Caching

  16. Memcached or Redis

  17. None
  18. Optimize database Optimize runtime A void A void

  19. Varnish

  20. Hit rate?

  21. Cookies?

  22. Cache Control?

  23. Developers Sysadmins

  24. None
  25. ✓State ✓Performance ✓Scalability ✓Cache invalidation ✓Architecture People often forget

  26. Who writes the VCL?

  27. Varnish still considered a sysadmin responsibility

  28. None
  29. Coaching developers & sysadmins

  30. ✓No state unless required ✓Cache-control discipline ✓Chop pages into content

    blocks ✓AJAX or ESI ✓Reasonable cache variations ✓Cache invalidation strategy Advice for developers
  31. ✓Normalize input ✓Cookies blacklist/whitelist ✓URL blacklist/whitelist VCL

  32. When you respect HTTP

  33. Developers are bridging the gap too

  34. Collaboration & empathy AKA  DevOps

  35. Architecture

  36. Service Oriented Architecture

  37. REST Cacheable   in  Varnish  if   done  right

  38. Monolith vs Microservices

  39. Distributed systems

  40. Big Data & NoSQL

  41. Async, concurrent & non-blocking processing

  42. Common goal

  43. Better end-user experience

  44. Frameworks & CMS’es

  45. None
  46. Bullet proof?

  47. Well-designed software should be more scalable

  48. Well-designed software should be faster

  49. Well-designed software doesn’t need much caching?

  50. Always cache … when you can

  51. Well-designed software doesn’t require much VCL

  52. Well-designed software knows how to purge the cache

  53. Challenges

  54. Caching state of mind

  55. Purging

  56. There are only two hard things in Computer Science: cache

    invalidation and naming things. —- Phil Karlton
  57. SSL termination +  SSL   awareness  in   application

  58. Static assets To   cache  or  not   to  cache?

    Invalidate   or  not?
  59. Clustering & HA

  60. Varnish flow

  61. None
  62. None