Constellation hands-on L3

 Learings from Characteristics of Constellation Architecture

The Constellation UI employs a Center-out™ approach. It is API-first, built on a model-view-controller (MVC) architectural framework and interacts with users through a prescribed UI in a stateless manner.

 Model-view-controller (MVC)

• The model is responsible for modeling data and business logic.
• The view manages the presentation layer and user interactions.
• The controller is the connection between the model and the view, and handles user inputs which it translates into appropriate actions in the model.

model - Pega Platform and its data, business logic, and workflow

view - Constellation design system front-end User Experience

controller -architecture orchestration layer is the Controller which conencts model to channel using API - Digital Experience (DX) API.

Microservices

Designing software applications as a collection of small, self-contained, and autonomous services

 The design of each service is small and responsible for a single specific end-to-end business function . They operate independently of each other and through well-defined interfaces

limits the impact of changes in one service on the overall system.
each service can be scaled individually based on demand

Stateless architecture

Each interaction (request) between client and server occurs as a separate transaction
Server does not maintain any state information about the previous interactions

Constellation architecture shifts towards stateless architecture, which results in ending requestor sessions and releasing the Pega Clipboard after each DX API call.

Client orchestration
generation of the UI and orchestration of UI components from the server to the client side

All the modules responsible for generating UI and orchestrating actions are in client and communicates with the server only to exchange information

User interface rendering are carried out fully on the client device by the Constellation design system

Prescribed UI

Ensures consistency across different parts of an application, or multiple applications within the same ecosystem.

all of the elements are built from the same library of prescribed components

Modular architecture

Designing software around smaller, reusable modules - each module houses a specific functionality and provides an interface to interact with it

Pega Infinity fully supports a modern, modular approach to application building, which enables the grouping of collections of Rules that address specific purposes into reusable modules.

Center-out

focuses on delivering customer and business outcomes by defining Microjourneys® to reach those outcomes

API-first

Designing applications prioritizes designing and building an API before working on any other aspects of the application (such as user interface or backend components).

Pega Constellation applies DX APIs to provide a standardized way of interacting with Pega Platform through a set of model-driven APIs.