How Doctrine Caching Can Skyrocket Your Application
summary
Explains concrete wins and limits: Doctrine 2.5 Second Level Cache stores identifiers and raw values (not hydrated objects) and cuts database round-trips; enabling metadata + query cache yields an immediate performance spike; result cache saves SQL result but still requires hydration; caching modes are read-only, non-strict readwrite, read/write (locks required); tracking policies include deferred implicit/explicit and the fastest notify tracking policy which requires manual change notifications; limitations: single primary keys, cross-process invalidation needed, hydrated-entity caching is fragile.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:28WHAT IS DOCTRINE
- 12:01ENTITYMANAGER
- 13:10TRANSACTIONAL WRITE- BEHIND
- 16:48HYDRATION
- 23:11TRACKING CHANGES
- 24:52CHANGE TRACKING POLICIES
- 28:17FURTHER IMPROVEMENTS
- 39:57HYDRATED RESULT
- 40:08REPOSITORY DECORATOR
- 41:47SECOND LEVEL CACHING
- 46:13QUERY CACHE: DELETE / UPDATE QUERIES
related talks
37mDemystifying cache in Doctrine ORM
59mHow much database abstraction do I need?
59mDoctrine ORM Good Practices and Tricks
01h 04mCaching Best Practices
42mSymfony Cache: a premium recipe to fast apps
45mCaching in Applications Still Matters
26mCache Strategies with Best Practices
43mCache Me Outside - Caching Methodologies & Architectures