Hello all,
I have found some variations between the documentation of the patterns courses
https://www.outsystems.com/training/courses/68/architecture-patterns-in-outsystems/?LearningPathId=8
and the official documentation,
https://success.outsystems.com/documentation/best_practices/architecture/designing_the_architecture_of_your_outsystems_applications/integration_patterns_for_core_services_abstraction/
is it due to an update of the latter?
Thanks a lot
Hi, which part specifically do you find to be contradicting? As far as I see, first source is some general high overview. Second source is a detailed architectural options list for Integrations with external systems specifically.
Hi, the first difference is that the names are different, and in some specific ones, such as direct integration, that the name is the same, in the course documentation it calls an api and in the second documentation it is the case simpler than ECS. In this case, if the certification asks what is the direct integration pattern to which we resort?
1: Path
2: Documentation
You are right, in this particular case there is some ambiguation ;)
SHORT: In the first source they refer to "Direct" vs ESB and in the second: as "Direct" as a sub type of the broader "Direct" category (if defined so in the first source).
LONG: In the first source what they mean is Direct vs ESB (or another form of external communication layer):
In this sense, everything from the second source is "Direct". And on the picture they have shown Real-Time Sync as an example from the "Direct" patterns of integration:
But they could have used any other pattern from the second source as an example.
No worries, I doubt there will be something that specific and ambiguous in the test, but if it happens there is: you can always reach out to them and explain. I am sure they will understand ;)