Passer directement au contenu principal

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice

Tableau blanc | 04:50

Streamline Digital Transformation with Pega's Situational Layer Cake

Pega’s Situational Layer Cake is a patented architecture that balances reusability and customization, essential for digital transformation and modernization. By structuring applications in layers—such as enterprise, core application, and product-specific layers—businesses can avoid redundant code and application sprawl, enabling consistent, efficient solutions across regions, products, and compliance needs. Learn more about how this approach simplifies managing complex variations while maintaining economies of scale.

Hi, I'm Don Schuerman, Pega CTO. And if you talk to us enough, you've probably heard about the Situational Layer Cake. Now, no, Pega is not trying to go into the baked goods business. And yes, it's maybe a little bit of a funny name, but it reflects a patented architecture that is absolutely essential to how you think about your digital transformation and legacy modernization. You see, the goal of the layer cake is to allow you to balance what are often two competing forces in your business. First is the desire to have reuse so that you get economies of scale and consistency. But on the other hand, you need to allow for the variation that your business requires. Sometimes you sell different products, you wanna be competitive. Sometimes you operate in different regions. You need to adhere to the regulatory compliance needs in those regions. The layer cake allows you to balance those in a way that traditional approaches don't. Too often you're either trying to stick everything in a single application, and you end up with a bunch of spaghetti code with all the if-then-elses needed to manage the variations, or you end up having each variation deploy its own app and you end up with 50 to 100 different apps, all of which do mostly the same thing. The layer cake is approach to avoiding that, and you start by building your application in layers with an enterprise layer. So think of this as all the pieces that can be reused across your enterprise. Maybe that's your data structures and interfaces. Maybe it's the definition of some key security elements in your application. Maybe you've built some reusable components that you wanna have available as a component library for people to use, maybe like how you generate a document or publish certain pieces of information into an event queue. So above your enterprise application, you might then build a layer with your application. So say you are building a new business application that handles how you onboard new customers. Well, as part of that application, you would define your workflow, or what we would call your case life cycle, for the steps that that new business process needs to go through in order to reach its outcome, its fulfillment stage. And so now I have a core application that can work across new business. Now, of course, I don't just do generic new business, I have different products. So maybe if I'm a bank, I have a lending version of my new business application. And I don't rewrite my whole new business application, I just define the pieces of that application that need to be specific for lending, how maybe I fulfill the loan at the end with specific documents and some of the underwriting decisions I need to make. And maybe I've taken my lending business into the UK. And as part of that, I know that, at the beginning of the process, I need to collect some information that is distinct in order to manage the loans for the UK. Now, when the application is run or executed, the layer cake looks across all the layers and finds the most specific stuff possible, and it dynamically assembles the right process for a user trying to onboard a new loan in the UK. And it does that without you having to write a bunch of if-then-else logic embedded into your processing code, or without having to have different applications at each layer of the layer cake. This architecture is incredibly powerful. AIG, the global insurer, they used to have 52 different claim systems deployed across the globe. They consolidated those 52 claim systems down to one, they call it one claim, using this exact architecture in order to do it. If you're thinking about doing digital transformation or modernizing your legacy systems, the layer cake approach is absolutely essential to ensure you don't repeat the siloed structures of the past, but actually build an architecture that's powerful enough to flex for both the variations you need in your business and the reuse that you need in an enterprise level to achieve your economies of scale.

Related Resource

Produit

Une révolution dans la conception d’applications

Optimisez et accélérez la conception de workflows, grâce à la puissance de Pega GenAI Blueprint™. Présentez votre vision pour générer votre workflow instantanément.

Partager cette page Share via X Share via LinkedIn Copying...