Modular architecture and Enterprise reuse

Enterprise reuse involves using the same software components, such as Rules, data structures, and processes, across multiple applications in an organization.

This approach offers several key benefits:

• Faster time to market
• Reduced effort and cost
• Improved quality and consistency
• Greater agility and control
• Better alignment across teams and initiatives

Together, these benefits contribute to a higher return on investment (ROI). Pega Platform is designed with enterprise reuse in mind. You can package and reuse assets, such as Data Types, Data Pages, Flow Rules, and integrations from the start. This reuse supports fast, scalable delivery across your organization.

In Pega Platform, Rules are the most basic reusable building blocks. Rules define how your application behaves. To encourage reuse, group related Rules into Modules. A Module is a self-contained application that delivers a specific business, integration, or utility capability. You can design Modules for reuse across the enterprise to support consistency, scalability, and maintainability.

Each Module contains reusable logic that developers can implement wherever the application requires it. Modules are independent of other applications, which makes them easier to maintain and update. You can tailor them to specific use cases by using parameters, extension points, and Configuration Sets. This approach enables teams to adapt functionality without duplicating work.

The Reuse Library in App Studio lists reusable assets in your application and explains how to use them. Adding Modules to the enterprise Reuse Library enables teams to assemble complex applications more quickly, which reduces development time and cost.

To include the assets of a Module in your application, you can either add the Module as a built-on application or use the New Application wizard. The selected method determines the extent to which you can modify the assets. Since modules are built for reuse, when you change a feature within a module, the change is visible in any application that reuses it.

The Situational Layer Cake™ approach organizes classes and Rules in a hierarchy to support reuse, specialization, and extension of application components.

The preferred design approach is the Modular Situational Layer Cake. In this model, the Enterprise layer stays lightweight and includes only shared assets (for example, UI styling, security, and authentication) that apply across the organization. Modules contain the most reusable functionality and align with specific business needs, system integrations, or utility functions. This modular setup promotes flexibility and reuse across applications.

In the following image, click the + icons to explore an example of Pega's Modular Situational Layer Cake:

To maximize reuse and ROI, it is essential to understand your business needs and design Modules at the appropriate level of detail. When an enterprise uses multiple applications, identify and reuse elements that remain consistent across those applications. For example, you can create the following types of modules:

• Data object Module: Business Modules include reusable assets focused on a single entity, such as a customer, account, and order.
• Integration Module: Integration Modules include reusable assets focused on integrating with a single system.
• Utility Module: Utility Modules include reusable assets that perform utility functions, such as document management.

Modules usually do not include Case Types because Case Types align with specific workflows and are challenging to reuse without extensions. This limitation makes updates harder to manage. To prevent changes, mark most Rules in a Module as Final. Use Configuration Sets to support behavior that requires customization.

Common reusable Modules include a Customer Module that enables users to search, retrieve, and update customer data and a Messaging Module that allows users to send and edit predefined messages.

In Pega Platform, App Studio and Dev Studio work together to streamline development and enhance collaboration. Developers create Rules in Dev Studio and mark them as relevant records to make them available in App Studio. In App Studio, designed for low-code users, teams can build features by using these relevant records. This interoperability allows business and IT teams to co-develop applications efficiently.

The following figure shows marking a Rule as a relevant record in Dev Studio:

Common building blocks used across Studios include Smart shapes, Data Pages, and Data Transforms. When you create records in App Studio, the system marks them as relevant, which makes them available across Studios. You can also use Configuration Sets in App Studio to adjust application behavior without changing the underlying Rules.

Check your knowledge with the following interaction: