FFLib Apex Common vs Apex Trigger Frameworks?

FFLib provides a full layered architecture including trigger handling via the Domain layer, whereas trigger frameworks focus only on trigger management. It offers broader separation of concerns and integrates with Service and Selector patterns.

How to handle CRUD/FLS in FFLib Apex Common?

Use the Selector layer with the new dataAccess arguments for USER_MODE or SYSTEM_MODE, as recommended in the December 2022 update. This deprecates the old enforceCRUD/FLS flags and improves performance by leveraging native Apex features.

Does FFLib Apex Common affect Apex CPU limits?

Yes, it can reduce CPU usage by using USER_MODE and SYSTEM_MODE for efficient queries and DML, as noted in the updates. However, the abstraction layers may add slight overhead compared to raw Apex.

How to migrate existing Apex code to FFLib patterns?

Refactor code into Service, Domain, and Selector layers incrementally. Refer to the 'Tips for Migrating' blog post and the sample application for guidance, but expect significant refactoring effort.

What are the dependencies for FFLib Apex Common?

It requires the ApexMocks library to be deployed first, as explicitly stated in the README. This is essential for mocking capabilities and the Application Factory to work correctly.

Is FFLib Apex Common compatible with Salesforce DX?

Yes, it was converted to Salesforce DX Source Format in April 2020, making it compatible with modern tools. The README mentions this and provides deployment options like the GitHub deploy button.

Open-Awesome

Apex Commons

BSD-3-ClauseApex

A comprehensive Apex library implementing enterprise patterns like Service Layer, Domain, Selector, and Unit of Work for Salesforce development.

GitHub

1.0k stars569 forks0 contributors

What is Apex Commons?

FFLib Apex Common is an open-source Apex library that implements enterprise application patterns like Service Layer, Domain, Selector, and Unit of Work for Salesforce development. It provides a structured framework to build scalable, maintainable, and testable Apex code by separating concerns and managing platform resources efficiently.

Target Audience

Salesforce developers and architects building complex, enterprise-grade applications on the Force.com platform who need a standardized approach to application architecture.

Value Proposition

Developers choose FFLib Apex Common because it offers a battle-tested, community-driven implementation of enterprise patterns specifically tailored for Salesforce's governor limits and security model, reducing boilerplate code and improving code quality.

Overview

Common Apex Library supporting Apex Enterprise Patterns and much more!

Use Cases

Best For

Implementing a clean architecture in Salesforce with separated business logic layers
Managing complex database transactions and DML operations efficiently
Centralizing and securing SOQL queries with field-level stripping
Building testable Apex applications with mockable service and domain layers
Enforcing CRUD/FLS and sharing rules in Apex code systematically
Migrating legacy Salesforce code to a more maintainable enterprise pattern structure

Not Ideal For

Salesforce projects with only simple automation and minimal custom Apex logic
Teams unfamiliar with enterprise patterns or layered architecture
Organizations with strict policies against third-party Apex libraries
Rapid prototyping scenarios where architectural overhead is undesirable

Pros & Cons

Pros

Proven Enterprise Patterns

Implements Service, Domain, Selector, and Unit of Work layers specifically adapted for Salesforce, ensuring clear separation of concerns as outlined in the documentation.

Efficient Governor Limit Management

The Unit of Work class optimizes DML operations, and Selectors centralize SOQL queries with security stripping, reducing governor limit consumption.

Integrated Security Enforcement

Supports native USER_MODE and SYSTEM_MODE for CRUD/FLS and sharing, with recent updates providing performance benefits and clearer intent over sharing declarations.

Enhanced Testability

Dependency injection via Application Factory and integration with ApexMocks allows for comprehensive unit testing and mocking of business logic layers.

Cons

Breaking Changes History

Significant updates like the April 2021 domain split and December 2022 deprecations require code migrations, as highlighted in the README's 'IMPORTANT CHANGE' sections.

Complex Initial Setup

Requires deploying the ApexMocks dependency first and a deep understanding of the patterns, which can slow down project kickoffs.

Fragmented Documentation

Core guidance is spread across external blog posts and articles, rather than a centralized, up-to-date documentation site.

Frequently Asked Questions

Related Projects

Apex mocks

An Apex mocking framework for true unit testing in Salesforce, with Stub API support

Stars459

Forks235

Last commit2 days ago

Force DI

Generic DI library with support for Apex, Triggers, Visualforce and Lightning

Stars240

Forks100

Last commit8 days ago

Apex Commons Sample Code

Samples application illustrating the Apex Enterprise Patterns library

Stars217

Forks107