apex-enterprise-patterns's Introduction

Apex-Enterprise-Patterns

Service Layer

Unit of Work is a design pattern that reduces repetitive code when implementing transaction management and the coding overheads of adhering to DML bulkification through extensive use of maps and lists.
State - things that an onject knows about itself
Behavior - things that an object can do.
Variables - are used to sepcify the state of an object, such as object's name or type.
Methods - are used to control behavior, such as getOtherQuotes.
Object = Methods (behavior) + Fields (state)
class - a template or blueprint from which objects are created.
Object - instance of a class.
Class can contain variables and methods.
Variables are used to specify the state of an object.
each DML statement accepts either a single sObject or a list (array) of sObjects.
operating on a list of sObjects is a more efficient way for processing records.

public class
    for (variable : [soql_query] {
        // code block
    }
    for (variable_list : [soql_query] {
        // code block
    }

for (integer i=0, i<10, i++)
for (init_stmt, exit condition, increment_stmt)

@AuraEnabled - to call Apex method from a Lightning component.
Lightning components use Static signature
Lightning Data Service uses an object named force:recordData to perform CRUD interactions on records.
Controller file - stores Javascript functions
Helper file - best practice: put anything we might need to either call multiple times or be called from another function.