Skip to content

This repo hopes to better explain Separation of Concerns for Salesforce and how to leverage the Apex Common library to employ it in your org.

Notifications You must be signed in to change notification settings

Coding-With-The-Force/Salesforce-Separation-Of-Concerns-And-The-Apex-Common-Library

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 

Repository files navigation

How to Implement Separation of Concerns in Salesforce

The Separation of Concerns Wiki

Housed in this repo is a wiki that goes over how to implement Separation of Concerns in Salesforce. It explains the three layers in Salesforce that you should separate your concerns into (Service, Domain and Selector) and how to leverage the Apex Common Library to make implementing Separation of Concerns in your org considerably easier.


The Example Code

There is also some example code showing you how an application (in this case a help desk app) in a Salesforce org might separate its concerns. If you reference the code while reading the wiki it should aide considerably in learning how to leverage the Apex Common Library to implement Separation of Concerns in your Salesforce org.


How to Submit Feedback for this repo

If you believe there is any information missing from this guide or that it needs more info in certain places, please submit an issue on this repo here and I'll add it ASAP!

How to Say Thanks

If you enjoy this repo and would like to say thank you, feel free to send a donation here! But no pressure, I really just do this for fun!

About

This repo hopes to better explain Separation of Concerns for Salesforce and how to leverage the Apex Common library to employ it in your org.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages