Mastering the OutSystems Architecture Certification (ODC): Tips & Tricks

This session isn’t about theory—it’s about practical preparation techniques that will help you confidently tackle the exam.

We have two expert speakers sharing their proven strategies:

🔹 Ashish Rout – A seasoned architect who has led multiple projects and helped many professionals achieve their certification goals. With over a decade of experience, he’ll share insights to strengthen your architectural knowledge.

🔹 Neha Shaikh – An experienced trainer, active community member, and holder of 14 OutSystems certifications. She has a deep understanding of tackling tricky exam questions and will guide you on how to approach them effectively.

If you're preparing for the OutSystems Architecture Specialist Certification (ODC), this session is a must-attend!

📅 Don’t miss out—learn from an expert and set yourself up for success! See you there! 🚀

1. Why Is Architecture Important? 1 Drives Consensus Manages Complexity Reduces Risk Supports Planning Facilitates Change Reduces Costs

2. What is available inside an App? 4

3. What is available inside a Library? 5

4. Reusing Elements Across Apps and Libraries 9

5. Reusing Elements Across Apps and Libraries 4

6. Business agnostic Highly-reusable Do not store data Library: A Business Agnostic Asset 5

7. Independent development for producers. Update control for consumers. Libraries Versioning 9

8. Apps are packaged into loosely coupled containers Only weak references are allowed between apps Publishing Two Apps 6

9. Libraries are packaged with each consumer app Consuming elements from Libraries create strong references Publishing Libraries 7

10. Choose the revision of the app to deploy Select Revision 9

11. Analyze the impact of deploying the revision to the target stage Impact Analysis 10

12. Stage Deployment stages organized on a pipeline App What users can create and manage in OutSystems Revision Snapshot of the app that is published on ODC Studio Terminology 13

13. Encapsulate role-related logic in Service Actions Reference the Actions and use them in other apps Create a role with the same name in all apps Inside each app use the local CheckRole action Grant access to all roles for each user in ODC Portal Roles Between Apps Roles are not Public and cannot be shared between apps 8

14. Architecture Patterns 14

15. Why Architecture Pattern? 7

16. Distributed Transaction Pattern 7

17. Distributed Transaction Pattern 7 Orchestrate your application Learn to visualize in a sequence diagram Retry before you move to compensation compensation is same as reversing always try to retry before compensation Asynchronous compensation through timer

18. Integration Pattern 7 Integration with Cold Cache & Real-time Sync Transparency Microservice pattern

19. Sharing Data Pattern 7

20. Sharing Data Pattern 7 Sharing Data between Apps Sharing Business Data with Business Rules

21. Library Reusable Pattern 7