Design Patterns in Saleforce.com
Design Patterns in Saleforce.com:
1. Singleton - minimizing object instantiation for improved performance and to mitigate impact of governor limits
2. Strategy - defining a family of algorithms, enscapsulating each one and making them interchangeable and selectable at runtime
3. Decorator - extending the functionality of an sObject in Apex
4. Facade - simplifying the execution of classes with complex interfaces (e.g. web service callouts)
5. Composite - treating a group of objects in a similar manner to a single instance of that object
6. Bulk State Transition - efficiently tracking the change of a field value in a trigger and executing functionality based on this change
1. Singleton - minimizing object instantiation for improved performance and to mitigate impact of governor limits
2. Strategy - defining a family of algorithms, enscapsulating each one and making them interchangeable and selectable at runtime
3. Decorator - extending the functionality of an sObject in Apex
4. Facade - simplifying the execution of classes with complex interfaces (e.g. web service callouts)
5. Composite - treating a group of objects in a similar manner to a single instance of that object
6. Bulk State Transition - efficiently tracking the change of a field value in a trigger and executing functionality based on this change
Comments
Post a Comment