Open-sourcing D'fflib
Why Deloitte decided to open-source their enriched version of fflib.
Highlights & takeaways
Deloitte decided to open-source our enriched version to contribute back to the community, connect with other passionates, simplify an intellectual property challenge and connect with organisations who might welcome support.
Rationale to open-source
Significant enrichments
Since 2016 we have been applying and extending the original fflib (apex-common) framework within our projects. This resulted in quite some significant changes like a full trigger and test factory builder framework and multiple efficiency improvements, both performance and developer usage wise.
Challenges to contribute back
The Apex Enterprise Patterns (AEP) repositories operate under a different mindset, with a hard backward-compatibility requirement and different framework principles regarding intentional design for theoretical correctness. Combined with limited response and activity on contributions over the past years, Deloitte, then, consciously decided to release D'fflib separately, as a full framework of its own.
The AEP Core team responded positively to our initial outreach, acknowledging the different framework principles and responsiveness,
and requested to position D'fflib as an extension rather than a replacement, as this would avoid confusion in the Apex Developer Community.
After some careful consideration and successful collaboration, all pre-requisites were met to ensure clear separation of concerns.
Allowing us to offer our enrichments with the community, without acting as a replacement for fflib.
Resolve intellectual property challenge
When applying D'fflib in our projects, we always faced 'intellectual property' challenges when collaborating with other implementation vendors, or returning maintenance to the client. We didn't want to commercialise the framework, given our gratitude to the original open-sourcing of the FinancialForce-based library. By open-sourcing, we mitigate these challenges, as D'fflib becomes community-driven, and thus not tied to any single entity's intellectual property.
Quality & Collaboration in Developer community
We are proud of our focus for quality by our strong developer community, and are happy to share that to the public. We would love to see this framework become community-driven (only initiated by Deloitte) and strengthen this joined framework even further by combining the passion for 'proper code' and improving the overall quality of Salesforce deliveries to eventually improve platform customer satisfaction.
Offer supporting hand
Based on individual responses, we've noticed quite some organisations do implement fflib, but struggle with the proper adoption and gaining the full benefits. Either by limited team knowledge, simply not knowing where to start/what full benefits could be, or not having a clear defined approach in combination with limited capacity. To those organisations we would like to offer support by means of this extensive documentation, or
Maturity Assessment (1 day)
- Automated scan to identify current maturity of your (D')fflib implementation
- Report with concrete steps and corresponding benefits these would unlock, incl. voice-over
- Optional interviews with your development team to properly understand their challenges/approach.
Click for more info.
Tailored trainings (4 hours to 2 days)
Depending on your need we can provide tailored training sessions (remote or on-site) to get your team enabled to maximise usage of the framework.
Click for more info.