Frequently Asked Questions
This page centralises common questions and answers about D'fflib, grouped per category.
General
The name is rooted in fflib-apex-common — the open-source framework D'fflib builds upon.
Keeping fflib in the name was intentional: it pays homage to its origins and reflects that D'fflib would not exist without the foundation fflib established,
while preserving familiarity and findability for anyone already working with it.
The D' prefix brings a few meanings together. It carries a quiet nod to Deloitte being the initiating company,
and for the mathematically inclined, the apostrophe reads as a prime symbol (′), as in f′ ("f-prime"), marking D'fflib as the derivative of its origin.
Altogether, this allows a clear spoken distinction on "the derived fflib" aka "the fflib" in comparison to the original fflib.
Contributions, bugs and feature requests
We welcome all contributions from the community! You can reach out first to align, or directly fork the repository and submit a pull request. Please check the Contribution Guidelines for more information. Following them allows us to process contributions swiftly and gives other community members clarity about the context, reasoning and potential impact of each change.
If you have an idea for a new feature or improvement but don't have the time or intent to implement it yourself, please share it with the community by submitting a Feature Request in GitHub Issues.
Please report it in GitHub Issues, clearly describing the context, situation, expected outcome and steps to reproduce. If you don't receive a timely response, feel free to reach out directly via one of the channels on our Support page.
Check our Support page to find the best channel to reach out to us or the community.
Installation and upgrades
There are multiple reasons for D'fflib being provided as unlocked packages:
- Simplified install & upgrade
Installs and upgrades complete in minutes via Salesforce link, rather than manual metadata retrieval and saving. - Reduced project impact
Code doesn't need to reside in your repository, keeping it cleaner.
Unit tests only run during install/upgrade and "all tests", not during regular deployments. - Full visibility & developer control
Code can optionally be retrieved for learning, debugging and encouraging community contribution.
Or stored in a local folder to enable AI suggestions. - Flexibility to customise
Projects can override package classes to apply project-specific modifications or test new features. Especially since most currentfflibprojects have made customisations, this simplifies the migration to D'fflib.
Note: overriding is not recommended unless necessary, as it may complicate future upgrades.
Unlocked packages do count towards your org's character limits, but the benefits of control and visibility outweigh this. If you have concerns, please reach out so we can discuss and optionally provide a Managed Package.
Despite the ambition and intent for modular setups, we've concluded this isn't feasible at the moment. Mostly due to the tight interdependencies between the various components which would make it hard to guarantee stability and compatibility across all components. Though this is definitely a roadmap item.
Until then, the repository is already split into folders per feature for readability and maintainability,
allowing local customisations to implement only the desired feature. For the easy-install unlocked packages,
we provide the default "D'fflib" package (including the latest of fflib-apex-common and fflib-apex-mocks)
and a "D'fflib BYO" (Bring Your Own) extension-package, only shipping D'fflib capabilities.
Since the D'fflib full package is defined by the combination of fflib-apex-common, fflib-apex-mocks and
our extensions, it effectively includes all the original fflib classes as well.
We've consciously decided to not remove the fflib classes for which we provide extensions
(like fflib_Application, fflib_SObjectDomain and fflib_SObjectUnitOfWork)
to avoid 'messing' with the core-classes, as developers installing the package might expect the classes.
This does imply that auto-completes may show the original fflib classes alongside the D'fflib extensions. In case community feedback suggests that this causes confusion or issues, we may revisit this decision in future versions.
No, that is not needed. It is possible to install the full D'fflib package and override the fflib classes via your normal deployment process. This reduces package dependencies and maintenance, while allowing you to apply project-specific customisations. However, when deploying only the delta of changes, be aware that you must re-deploy the overridden classes each time you update the D'fflib package.
Share your customisations so we can consider incorporating them into future versions of D'fflib, benefiting the wider community, while simplifying your own project setup.
Legal & licensing
D'fflib is licensed under the same BSD-3-Clause licence as fflib, which is a permissive open-source licence
that allows you to use, modify, and distribute the software, as long as you comply with the licence terms.
The full licence text can be found in the LICENSE file.
Yes, there are no restrictions on types of projects, nor royalties or fees based on how the software is used — as long as you comply with the three licence conditions.
When using D'fflib, you must retain the copyright notice and licence text in your source code. If you redistribute it in binary form (e.g. as part of a packaged product), you must also reproduce the notice in your documentation or distribution materials. You may not use the name of Deloitte or its contributors to promote derived products without written permission.
D'fflib is provided "as is", with no warranty or formal support obligation or SLA. The community actively maintains the framework and we do everything in our power to ensure everyone is enabled and no regression issues occur due to the D'fflib framework. That's why the framework is rigorously tested for backward compatibility with previous versions.
There is no dependency: you can fully install and apply the framework without any interaction with Deloitte. Usage will always remain free of charge, as will updates, given the community-driven nature of the framework. The only relation to Deloitte is them being the initiators of D'fflib, and offering optional maturity assessments and trainings to help maximise the utilisation and ROI of the framework.
Project relevancy
The layered architecture guides developers to separate concerns and responsibilities, meaning each method or class has a single responsibility. This makes the code easier to understand, test, and modify without affecting other parts of the codebase. A clear example is bulkifying methods (accepting a list of records rather than a single record), which enables future use cases where the same logic needs to run across multiple records without any refactoring.
Yes! A well-structured codebase becomes more valuable when using AI tools, not less.
AI tools like GitHub Copilot, Claude Code, Cursor or similar assistants work significantly better when your code is consistently structured, well-named and following clear conventions. A codebase with D'fflib applied gives AI unambiguous context, as well as a lower risk of one change unintentionally breaking other functionality, due to adherence to SOLID principles. This leads to lower token usage, less "explain this to me" back-and-forth, and more accurate first-time-right suggestions.
Additionally, D'fflib ships with full documentation and a set of ready-to-apply AI skills, directly strengthening AI tool responses for framework-specific patterns.
Finally, while AI is here to stay, there is a risk in fully transferring control to AI with no backup plan. If token costs grow, tokens run out, or AI tools are unavailable, a well-structured codebase still allows your team to do the work manually when needed.
In short: the framework doesn't only enable humans, it multiplies the value from AI agents as well, while ensuring robust and future-proof delivery.
If your project truly has no code, there is no need to install D'fflib.
Even with a small codebase, installing D'fflib provides benefits in terms of structure, maintainability, and scalability. It helps ensure that as your project grows, your code remains organised and easy to manage.
For larger codebases, D'fflib can be particularly beneficial for improving maintainability and scalability,
and can also significantly reduce technical debt and unit test runtimes, improving delivery velocity and reducing costs.
Introducing a new framework into an established project can feel daunting, but fflib has been adopted at a late project stage many times
with significant improvements as the result. D'fflib can be introduced iteratively, starting with small refactorings,
to let the team get familiar and gradually adopt. This is fully explained in the Adoption guide,
and we are here to support you in that journey.
Others / Contact
Still have an open question after reading this page and searching the docs?
Check our Support page to find the best channel.