Has this been your reaction when trying to navigate your path around design patterns especially when it involves patterns governing integration !! Well to be honest technical jargon always gets to my nerves , but after the initial jerky reaction I always take it upon me to demystify / simplify it.
So what are "Design Patterns"?
As per Wikipedia - A design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. A design pattern is not a finished design that can be transformed directly into source or machine code. It is a description or template for how to solve a problem that can be used in many different situations.
1. Evaluate the vulnerability of the area under inspection
2. Find the steps to reduce damage and vulnerability
3. What would be the precaution each can take.
4. Have an advance warning system if possible.
5. Formulate a relief and rescue strategy
So be it a earthquake/ floods or any other natural calamity the basic steps will follow above pattern.
What are the main types of design patterns?
- Algorithm strategy patterns
- Computational design patterns
- Execution patterns
- Implementation strategy patterns
Another school of thought goes by the following classification:-
- Creational Design Pattern
- Structural Design Pattern
- Behavioral Design Pattern
Lets leave the general design pattern and dive into design patterns associated with SFDC Integration.
1. Data - These service the need for taking or synchronizing data from one system to another. Mostly the purpose of these integration is to see that both system have meaningful data. These type of integration are supposed to be the simplest.
2. Process - Here the two different system target and source communicate to service a business process related requirement.These might require complex design and implementation and involve multiple systems, where the one invoking the other systems may be the controller while other act like members of an orchestra .
There are certain things which need to be considered while embarking over a type of design pattern. the main considerations are:-
1. Source / Target systems
2.Type of integration (Data/ Process)
3.. Timing (Synchronous/ Asynchronous)
We would deep dive on those aspects in a followup blog.