During the last 5 years, many popular media players moved from CMS to low-level FrameWorks such as Symfony, Zend, Laravel. Some of them even dropped PHP in favor of new languages like Node or Python.
They all had the same motivation : “web performances”, understanding response time, scalability and stability.But is that the best solution?
In this talk, Gilles Guirand explains exactly why now is the time to reconsider PHP CMS, from the devOps culture to the metrics-centric approach, from the authenticated cache to CDN, from back-end to front-end optimization.
6. FIRST GENERATION
eZ3 eZ4
(own cache)
end
User
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
YES
ALMOST
YES (blocks)
NOOOOO
2003 ~ 2010 : Industry needs rapid website builders
Cache-blocks
viewcaches
PHP caches
7. SECOND GENERATION
eZ4
(own cache)
end
User
2008 ~ 2012 : Industry faces the high-traffic (rescue strategy)
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
NO ( Time To Live )
NO
NO (Full page - static)
YES
Static
cacheCache-blocks
viewcaches
PHP caches
8. THIRD GENERATION
eZ4+ext.
eZ5
(HTTP cache)
end
User
AFTER ~ 2012 : Industry needs hight trafic + auth. users (UX time)
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
YES
YES
YES
YES
eZ Accelerator not OSS / no Auth
eZ5 cache a bit late
10. THIRD GENERATION
end
User
after ~ 2012 : Industry tried alternatives (pure PHP FrameWorks)
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
YES
YES
YES
YES
11. THIRD GENERATION after ~ 2012 : Industry tried to combine (best of all worlds)
end
User
eZ
admin
UI
Front-endBack-office
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
YES
YES
YES
YES
12. THIRD GENERATION after ~ 2012 : Industry tried to combine (new APIs design patterns)
eZ
admin
UI
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
YES
YES
YES
YES
REST
API
end
User
13. THIRD GENERATION after ~ 2012 : Industry tried to combine (best of all worlds)
eZ
admin
UI
Front-endBack-office
Dynamic cache invalidation
Authenticated cache
Fragmented cache
High traffic capability
YES
YES
YES
YES
end
User
19. Static ESI HTTP cache
Dynamic purge
Authenticated cache
HEADER
FOOTER
breadcrumb
User profilingContent listContent list
ANONYMOUS
ANONYMOUS
ANONYMOUS
USER GROUP USER
ESI
eZ5 cutting edge
ESI
ESI
ESI
95% HITS
eZ
52. Back
end
Static ESI HTTP cache
Dynamic purge
Authenticated cache
HEADER
FOOTER
breadcrumb
User profilingContent listContent list
ANONYMOUS
ANONYMOUS
ANONYMOUS
USER GROUP USER
ESI
A perfect project ...
ESI
ESI
ESI
95% HITS