Details About Separation of Concerns | Salesforce Developer Guide

At the point when You Don't Need SOC on Force.com

One critical advantage of Force.com is its definitive improvement model that allows you to make objects, fields, formats, approval rules, work processes, recipe fields, thus substantially more without composing a solitary line of code. Explanatory improvement is quicker and simpler, and it as of now executes a level of SOC. In the event that your application is intensely information-driven, and you can convey a huge piece of your application definitively so don't reproduce the wheel, simply use it! 

Despite the fact that it's not code, what you can accomplish with explanatory advancement is still a lot of an engineering layer in your application, which we'll discuss all the more later. 

Don't forget to check out: Understand Separation of Concerns Unit | Salesforce Developer Guide

When to Use SOC on Force.com 

In the event that your application is measure-driven or you are getting pushed to carry out more complicated computations, approvals, or more extravagant UI encounters, you'll adventure into the place where there is Apex code. Force.com gives many spots to put Apex code, similar to triggers, Visualforce controllers, APIs, Batch Apex, and email regulators.

You can make a colossal interest in creating and testing code, however, it's the business rationale that you are generally worried about ensuring. We investigate a few rules for composing business rationale sometime in the not too distant future yet for the time being think about the accompanying occasions for utilizing SOC on Force.com. 

Supplanting or adding one more UI to your application — Consider how much code you need to revamp or port that steers clear of the UI yet influences your application's embedding, refreshing, approving, and computing usefulness. 

Giving a public-confronting API to your rationale — Assess what portions of your current code base you would call to carry out the API. Is utilizing your activity techniques in your Visualforce regulators a decent reason for an API? (The appropriate response is no.) 

Scaling your application rationale through Batch Apex — If you need to keep on giving an intuitive encounter (for more modest volumes) by means of your current UI, how might you divide rational among the two to guarantee that the client gets reliable outcomes paying little mind to the size? 

Working with complex activity strategies in your Visualforce or Lightning Component regulators — Does any of your code manage something beyond taking care of data to and from the client? With Visualforce and Lightning Components, you can parcel your code by means of Model–see regulator (MVC), a type of SOC for customer improvement. Anyway utilizing regulators for all your code doesn't ensure that you are following SOC as far as your business rationale. 

Making it simple for new designers to discover their direction around your codebase — How much time does an engineer have to realize where to put new code and discover existing conduct? 

Check out an amazing Salesforce video tutorial here: Salesforce Career Path 2022 | How to Make Career in Salesforce

Contingent upon where you have composed your code, you may as of now be fit as a fiddle to handle a portion of the above situations. If not, or on the other hand in case you're simply inquisitive, the forthcoming units shed some light on the additional ideas. The accompanying table can likewise assist with concluding whether to utilize these examples dependent on the size and extent of the arrangement that you're building.