consider PHPCR as the storage API for the product catalog

[lsmith77]

PHPCR is an adaptation of JCR, the Java Content Repository specification. This specification essentially defines an API for the CMS problem domain:
http://phpcr.github.com

It covers handling unstructured data inside a tree structure with support for referencing nodes via UUIDs and node types to be able to optionally define a data schema. It also includes features like versioning, ACLs, observation and full text search.

There are multiple implementations of PHPCR already (pure PHP, C extension, Java) which make it possible to scale the storage implementation to the needs and available resources of end users without having to touch the business logic.

With PHPCR ODM there is also an optional convenient data mapper layer that can sit on top of any PHPCR implementation which adds native support for i18n.

[magento-team]

Thanks for the suggestion, however I don't expect such significant changes to happen in Magento 2 regarding storage. We are focusing on MySQL as as data storage for all kinds of data (except cache etc)

[lsmith77]

PHPCR can also work on top of MySQL. I assume you are looking into replacing EAV in Magento2 and PHPCR would be the perfect fit for exactly those parts that are currently using EAV.

[Koc]

ping @mage2-team

[zerkella]

Reply from 209.15.239.51: bytes=32 time=115ms TTL=47