PHPCR
A (BETTER) WAY TO STRUCTURE YOUR CONTENT
PFCongres 2013 Uncon - 14 september 2013
Slide 2
Slide 2 text
WILLEM-JAN ZIJDERVELD
PHP DEVELOPER AT BEELDSPRAAK
Twitter: @willemjanz
Blog: blog.willem-jan.net
Github: github.com/wjzijderveld
Email: [email protected]
This is my very first talk, please be gentle
Slide 3
Slide 3 text
WHAT'S THIS TALK ABOUT
PHP CONTENT REPOSITORY
Why would I need PHPCR
What is PHPCR
Who is using it
When to use it
When not to use it
Slide 4
Slide 4 text
WHY WOULD I NEED PHPCR
CMS data isn't always structured
NoSQL isn't always a fit, but has similarities
Makes it easy to switch storage engines
A lot of build-in features
Slide 5
Slide 5 text
WHAT IS PHPCR
Ported from for TYPO3/Flow3
Removed JAVA overhead
Added PHP specifics
Some naming changed
PHPCR Utils
Tree of nodes
JCR-283
Slide 6
Slide 6 text
WHAT IS PHPCR
NODES
Nodes have a name and a type
A node has a path
Nodes can have named properties with values
Slide 7
Slide 7 text
WHAT IS PHPCR
WORKSPACES
Can be compared with branches in a VCS or with a filesystem
Slide 8
Slide 8 text
WHO IS USING IT
Jackalope (Jackrabbit/Doctrine-DBAL)
Symfony CMF
ServerGrove KnowledgeBase
TYPO3
Vespolina and Sylius
Midgard2
Slide 9
Slide 9 text
WHEN TO USE IT
Hierarchical data
With compound data; like attachments or translations
When you need versioning
When in need of FullText search
Slide 10
Slide 10 text
WHEN NOT TO USE IT
Strict structured data
Aggregation