Salesforce Lightning Platform Enterprise Patterns | Apex Enterprise Patterns

Apex Enterprise Patterns | Salesforce Lightning Platform Enterprise Architecture
Review basic Object-Oriented Analysis and Development themes
Salesforce Lightning Enterprise Architecture patterns
1) Selector Pattern
2) Domain Pattern
3) Service Pattern
4) Unit of Work Pattern
5) Application Factory Pattern
Review of Apex Enterprise Patterns Open Source group and frameworks
0:00 Introduction
2:09 Apex Enterprise Design Patterns.
4:42 Basic OOAD Themes
5:10 Separation of Concerns
8:25 DRY Principle
9:20 SOLID Principle
13:40 Dependency Injection
15:28 Apex Common Framework
16:20 Selector Pattern
36:45 Domain Pattern
49:05 Service Pattern
57:49 Application Factory Pattern
1:06:09 Salesforce DX Consideration
Check below blog post for more detail and link
www.apexhours.com/apex-enterpr...

[@apexhours]

Check this blog post for link and more detail www.apexhours.com/apex-enterprise-patterns/

[@akramomair]

Thanks for the session Amit!

[@apexhours]

Keep watching

[@puffsplus72]

Great session though and thanks!

[@apexhours]

Thank you too!

[@ragulhm]

thanks Amit.... Waiting for so long 👍🏻

[@apexhours]

Dont miss the live session

[@ragulhm]

How could i ask questions on live session ?

[@shivananda8796]

It's a very informative session. Thanks a lot for this :)

[@apexhours]

Glad you liked it!

[@phabove7]

How to avoid the risk of hitting 5 MB of heap size limit, when using Selector pattern? It will query many of the fields, which may not be needed, but will take lot of heap as the number of records go up.

[@orlybriceno]

That's a good point Omkar , I was wondering if you could specify which fields you wanted and if you wanted to bring related entities or not?

[@puffsplus72]

Good question!

[@shivananda8796]

Same Thought!!!

[@lenickramone]

I have the same feeling.
The level of complexity that it adds to the code looks like it is not worth at the end.
Sounds like adding a lot of OOP complexity just for the sake of imagining that it is more organized.
If you have any feature that you will need to add a new field, that is also true with the Selector Pattern.
So, is it really worth to adopt it?

[@manishtandon3171]

@@lenickramone Agree, this pattern is very complex to implement, Not Worth the time in my opinion! Gorgeous looks but doesn't adds that much value towards the end. Slows implementation...

[@phabove7]

If we always use mocks for testing, how can we make sure that our newly added code doesn't break the existing workflow. e.g. In case of actual insertion of data in @TestSetup method, if our recently added code or validation causes issues, it fails, so we know we have to fix the problem. In case of mock, isn't it almost never fail?

[@shivananda8796]

Exactly!!

[@si6tynin]

It would be great to have a session on Apex mocks.

[@apexhours]

We will plan soon

[@si6tynin]

@@apexhours Excellent. Even Daniel was mentioning about it in this lecture .Will wait for it.

[@stevenduong8126]

Thanks so much for sharing. Could you please advise if we have any community about this topic?

[@apexhours]

Let us know here. We can help you

[@stevenduong8126]

@@apexhours This lesson is just general ones and I feel that is not enough for me to implement in my real projects. Could you please make a series video how to implement properly in our ORG? Thanks so much for this video. I can leverage this foundation library and do more projects in our company.

[@si6tynin]

Is there any plan to have a session on Apex mocks?

[@apexhours]

we will plan soon

[@markdu2682]

where can i download or get the slides used by Daniel?

[@apexhours]

Search on ApexHours website

[@samsilva6602]

How do we cover the selector layer by test class since it is all mocked? hm do we stick to the standard test class?

[@apexhours]

you can use mock apex for same

[@samsilva6602]

@@apexhours my method is always returning empty results even though I set a return in the startstubbing :(
When I try for example:
Test.start();
List responseOppLst = new OpportunitiesSelector.selectByAccountId(new Set{mockAccountId});
...
This responseOppLst is always empty even though I set the mocked opp list in the startstubbing/stop mock.when() ... ThenReturn(mockedResponseOppLst). It seems like my selector is ignoring the mock and trying to find the records on Salesforce, but since it is a fake accountId, it returns an empty list :(

[@puffsplus72]

One big downside of this format vs zoom: no q&a at the end!

[@apexhours]

Feel Free to post your question in Comment. We would love to answers over there