DD4T & DXA Merging – Why it is happening?

Few weeks back, I got honored to attend my third MVP retreat and those who really thinks we simply drink beer during this retreat (as few of connection really reacted that way and asked If I am not too drunk can I help them with something :P), we indeed get a privileged to connect with great mind in the industry and SDL technologies and got a chance to collaborate on future of SDL and related technologies.

This year, the group focus was on taking out the best from DD4T and DXA and merge them in a new framework to get the best of both world and create more powerful framework – so a win-win situations for customers as well as vendors/partners/consultants involved in a typical SDL implementation.

Why this merging?
Few years back DD4T comes in existent to provide a framework with possible best practices to use while implementing a website using SDL Tridion system and MVC. This aims to provide a smooth and faster development and adapting to the developers faster who may not have much deeper knowledge of Tridion but MVC (.NET or Java side).

Followed to DD4T, another framework introduced to have already baked frequently used modules in website so as to provide a prototype of website and further reducing the development time. At the core this is also using most of DD4T – initially it is termed as Tridion Reference Implementation (TRI) later renamed to SDL Tridion Reference Implementation (STRI) and finally to Digital Experience Accelerator (DXA)

Both these frameworks were aimed to provide a short development time while still keeping the best practices recommended by the experts in the area and provides noobs a smooth and faster learning curve while meeting the company/customer objectives faster.

Now at one end SDL Tridion has gone through a tons of architecture changes and advancements in the form of SDL Web8 and at the other end massive improvements has been done in the DD4T as well as DXA – This has resulted in branching out of these two solutions from a common goal.

The End Result: Both DD4T and DXA are now competing each other where architects across companies are evaluating both DD4T and DXA to choose which framework to use – The initial aim was both of these framework to complement each other.

This prompts the team behind these two framework to collaborate and agree to combine these two frameworks in one powerful framework to further enhance the development experience.