Hello,

Have you already checked the course; each topic is explained there in detail- 

https://learn.outsystems.com/training/journeys/architecture-patterns-407

Also there  is further information where question is asked for more clearity.

https://www.outsystems.com/forums/discussion/69050/architecture-patterns/

Thanks
Tousif Khan

Extension Patterns: Use an extension to wrap an external library or wrap entities from an external database.

• Used for extending the functionality of the platform by incorporating custom code or third-party libraries.
• Ideal for scenarios where built-in functionalities need enhancement or customization.

Connector Patterns: Create a wrapper module for consumers and an extension to encapsulate the external API.

• Facilitate integration with external systems by creating reusable components that handle communication protocols and data transformation.
• Suitable for projects that require seamless integration with various external services.

Hi @Mohan Raj S ,
The Connector Pattern in OutSystems is used to integrate external systems, APIs, or databases. It allows applications to consume REST/SOAP services, interact with third-party platforms, or access external databases seamlessly. Connectors are typically built using Service Studio or Integration Studio and focus on data exchange, API requests, and response handling. They can operate on both the client and server sides, making them flexible for different integration scenarios, such as payment gateways, cloud services, or CRM systems.

On the other hand, the Extension Pattern is used to extend OutSystems' capabilities by incorporating custom logic written in C# or Java. Implemented via Integration Studio, extensions run exclusively on the server and enable functionalities that OutSystems does not natively support, such as complex computations, encryption, or third-party .NET/Java library integrations. Unlike connectors, extensions are not meant for external service communication but rather for enhancing the platform's core functionality with performance-optimized operations.
Thanks