Downloaded 11 times
Uploaded byVarnish Software
Thijs Feryn: Varnish - where devops & sysadmins meet
This document discusses caching and Varnish. It begins with an introduction of the author and their role advocating for Varnish. The bulk of the document then discusses challenges and best practices for using caching and Varnish, including topics like cache invalidation strategies, collaboration between developers and sysadmins, and challenges like purging, SSL termination, and static asset caching. It emphasizes that caching requires a different "state of mind" and that well-designed software and collaboration can help address many challenges that systems employing caching may face.
More Related Content
Similar to Thijs Feryn: Varnish - where devops & sysadmins meet
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Thijs Feryn: Varnish - where devops & sysadmins meet
- 1. Where developers & sysadminsmeet By Thijs Feryn Varnish
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. After a whileyou hit the limits
- 15.
- 16.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 25.
- 26.
- 27.
- 29.
- 30. ✓No state unlessrequired ✓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 ✓URLblacklist/whitelist VCL
- 32.
- 33.
- 34.
- 35.
- 36.
- 37. RESTCacheable in Varnish if done right
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52. Well-designed software knows how topurge the cache
- 53.
- 54.
- 55.
- 56. There are onlytwo hard things in Computer Science: cache invalidation and naming things. —- Phil Karlton
- 57. SSLtermination + SSL awareness in application
- 58. Staticassets To cache or not to cache? Invalidate or not?
- 59.
- 60.