To benefit from improved performance in DXA 2.2, is it possible to use the legacy DD4T data model instead of the R2 data model when upgrading from an older DXA version?
- Customer is on DXA 1.8 (Java), and would like to upgrade to DXA 2.2 (Java) for improved performance. - Customer would like to know if improved performance for page load time can be seen with using the legacy DD4T TBBs, to reduce the effort of the DXA upgrade.
The R2 data model is significantly more efficient than the DD4T data model. For DXA 2.2 used in conjunction with Web 8.5, the in-process standalone Model Service can and will convert legacy DD4T to R2 and vice versa, but this leads to less efficiency. Ideally, all content in the broker database should be in the R2 data model to have maximum efficiency, although this does allow republishing of content to be delayed or phased.
When upgrading from DXA 1.8 to DXA 2.2, it is necessary to modify the default and custom TBBs when switching to the R2 data model.