DELIVERING MICROSERVICES

BENEFITS WITH PEGA

TABLE OF CONTENTS

1 Introduction

1.1 Executive Summary

1.2 How We Got Here: A Brief History of Microservices

1.3 A Closer Look at Microservices: Small, Modular, and Well-Defined

2 The Fundamentals of the Pega Platform Architecture

3 Enabling Agility: Pega Features with Microservices Benefits

3.1 DevOps

3.2 Componentization

3.3 Technology Heterogeneity and Compatibility

3.4 Pega Cloud Choice

4 Microservices Architectures – A Reality Check

4.1 Not a Silver Bullet

4.2 Reuse and Organizational Scale

4.3 From Low Code to No Code

4.4 Integrations

5 Summary

IMPORTANT NOTICE

The Information provided in this paper is not a commitment, promise or legal obligation, including to deliver any material, code, or functionality
and the development, release and timing of any features or functionality described for our products remains at our sole discretion.

1 INTRODUCTION
1.1 Executive Summary
This white paper is intended for technology professionals
looking to adopt microservices architectures to speed time
to value in their enterprise applications. The Promised
Land for many software architectures, microservices have
been proven to support the scale and speed demanded
by the world’s largest Internet platforms, such as Amazon
and Netflix. Established enterprises looking to adopt
microservices, however, must plan on how they integrate
this new approach with their existing legacy systems and
established processes. For over 30 years, Pega has been
helping enterprises bring speed and resiliency to their
enterprise applications by empowering business and IT
collaboration in a unified model-driven platform. The
Pega Platform provides a flexible and future-proof way to
connect legacy infrastructures to the digital world while
evolving your development processes to take advantage
of microservices, DevOps, and other more modern
approaches. Because Pega uniquely empowers business
Impact of Pega Platform
321% 75%
ROI Development
cost savings
4 | Delivering Microservices Benefits with Pega
and IT to jointly participate in how your applications are
built and changed, organizations are able to look beyond
microservices to the automatically generated software
applications that future competitiveness will require.
In this paper, you will read more about the emerging trend
of microservices and the business and technology drivers
behind it, as well as look at some of the challenges in
implementing microservices, especially within an existing
enterprise infrastructure. After a brief introduction to the
architecture of the Pega Platform, you will learn about
how the Pega Platform provides a flexible approach to
microservices that can be easily blended with your existing
infrastructure. We’ll discuss DevOps, cloud, and software
componentization and explain how a model-driven
architecture is uniquely suited to these technologies.
Finally, we’ll look at how the Pega Platform future-proofs
your investments, ensuring that you can deliver the
software architectures of today and tomorrow.
50% 75%
Reduced End-user
time-to-market productivity gains
1.2 How We Got Here: A Brief History of Microservices
Microservices are one of the hottest tech trends in
application development today. Business needs and new
technologies have paved the way for new approaches to
app development. Blended with cloud infrastructure, agile
development, and DevOps, these new approaches are
propelling a new age of rapid app development and digital
transformation.
Service Oriented Architectures (SOA) and microservices are
part of a continuous shift in how IT organizations approach
software development. Historical approaches, like monolithic
architectures and waterfall development, worked for large
projects that could be aligned against a predictable result.
The flexibility and scale of the cloud together with an
increased market need for rapid innovation have driven
business and IT stakeholders to become more collaborative
as rapid development requires more efficient and tight
business alignment. This has led to the development of a
new agile, DevOps culture of continuous delivery of features
and functionality directly aligned to business needs.
Software built with monolithic architectures and giant blocks
of code required a lot of overhead, time, and resources for
applications to be developed, deployed, and managed.
Waterfall vs. Agile Methodologies
WATERFALL
ANALYSIS
DESIGN
IMPLEMENTATION
TESTING
MAINTENANCE
1 2 3 4 5
In this model, business stakeholders would document
business requirements that were given to architects to
translate into technical requirements, which designers would
take and turn into wireframes, and developers and QA teams
would turn into code and test cases. The developers and
QA teams would have to work with IT operations to then
deploy the code to the production infrastructure and ensure
nothing was interrupted, performance was adequate, and no
issues were introduced with the release. QA would continue
to test and any features not implemented as required or
bugs were addressed at a subsequent release. The business
stakeholders and end customers would often see the end
results for the first time with the release.
The process was laborious and tasking for all teams involved.
Frequently miscommunication and misinterpretation would
occur along the way. Features delivered would often miss
the mark on what the business and customer expected or
needed. And this process could take months, sometimes
even years, to bring results to clients.
AGILE
DEVELOPMENT QA
UI DESIGN U&T
DEFINE CLIENT
REQUIREMENT FEEDBACK
NO – NEXT ITERATION YES – RELEASE
www.pega.com | 5
Evolution Image | Concept 4
Evolution of Application Architecture
MONOLITHIC TRADITIONAL SOA
The tightly coupled monolithic architecture of the 1990s
was not agile, fast, or resilient. One small change could have
unanticipated effects, requiring re-testing of every release
and change. In the early 2000's we saw the rise of SOA. This
allowed for elements in an application to be developed more
autonomously but still required tight coordination between
elements and teams to ensure each fit into the overall design.
As cloud become the dominant architecture, microservices
made their first appearance in 2010, enabling a decoupled
approach to application development. Microservices enable
continuous delivery of capabilities and usher in with it a
new age of rapid app development. For many enterprises,
6 | Delivering Microservices Benefits with Pega
1 2 3 4 5
1.3 A Closer Look at Microservices: Small, Modular, and Well-Defined
Microservices and Containers
MICROSERVICES
MONOLITHIC
All functionality This is scaled
is put into by replicating
single piece. onto multiple
servers.
MICROSERVICES
Each element This is scaled
is placed into a by distributing
separate piece. accross servers
as needed.
microservices have become the strategic approach to
software development, because they align IT more seamlessly
with the business, allowing for changing business needs
to drive development priorities. Adopting microservices
As we know, many application teams are moving to
architectures—and related approaches, such DevOps and
Microservices architectures are designed to enable microservices to achieve rapid and efficient development of
cloud architectures—is enabling enterprises to keep their
teams to develop applications rapidly around a applications and new features. They are doing this to derive
competitive edge, increase profitability, and ensure that their
specific business functionality, while maintaining the key benefits of agile development:
business units and teams are organizationally aligned.
resiliency. In a microservices architecture, every
ƒƒ Speed
element of functionality within an application is
Quickly develop, deploy, and update discrete functionality
separated into its own distinct service. To ensure this
independent of their functions.
separation is maintained, each microservice should:
ƒƒ Scale
1. Be independently deployable, capable of running Microservices are discrete enough to operate as separate
1
in a unique process
services but robust enough to be scaled across functions,
2.
2 Communicate through a well-defined, lightweight business units, and geographies. Microservices can be
mechanism, i.e., REST scaled independently to satisfy demand.
3. ƒƒ Safety
3 Scale cleanly across servers, replicating as
needed One alteration or failure does not lead to cascading
4.
4 Be expressed with business-oriented APIs. impacts or failures. Issues are isolated and changes can
be made discretely, without impacting or interrupting
5. Deliver a core functionality that is an asset to the
5 functionality across the application. DevOps ensures you
business
can rollback updates, fix bugs and redeploy quickly.
www.pega.com | 7

THE FUNDAMENTALS OF THE
2 PEGA PLATFORM ARCHITECTURE
The Pega Platform is architected for loose coupling and
high autonomy. Pega is a layered architecture but is not
a monolith, thus freeing it from the typical ailments of all
monoliths which require you to redeploy and recompile
before pushing any updates or alterations to production.
Pega’s model-driven approach starts by breaking down
business functions into manageable components. Each
function in Pega is captured in a fit-for-purpose visual
model. For example, one model type captures the logic of
a business rule in a “Decision Table.” Another strings user
steps and decisions together into a business process or
“Flow.” Another captures the deadlines and escalations
associated with a “Service Level.” Yet another model lets
a user define how fields are arranged on a web or mobile
screen. At run time, the Pega Platform receives a request
Pega Platform Architecture
Hiring App Job Application
Hire Me Application Case Model
Process Model for Job Application
8 | Delivering Microservices Benefits with Pega
(such as REST call or an HTTP POST) and uses a search
algorithm to determine the right models to execute in order
to fulfill the request. The engine extracts the right models
from a central repository (or shared cache) and executes
the models as Java code, either reading Java from the shared
cache, or, if needed, assembling Java from the models in
real time. Since the Pega Platform automatically generates
exactly the right Java code that is needed, we often refer to
it as software that writes your software. Additionally, from
a business culture perspective the model-driven, visual
approach to development breaks traditional silos between
business and IT. Anyone, including business stakeholders,
who understands the business requirements and goals can
use the model-driven approach to architect an application.
1 2 3 4 5
Pega’s architecture enforces a high degree of granularity in in an isolated, decoupled way. However, if you wish to run
the application design. It also demands specialization and
separation of functions: a developer cannot define UI logic
that same decision logic as a part of a larger process flow,
another Pega engine node can execute in the same memory
into a process flow or vice versa because the model types by space as the process logic, eliminating unnecessary latency
definition are fit for purpose. There’s no place to put UI logic between systems. The Pega engine can be containerized
in a process diagram. The models themselves are loosely using Docker to ensure new nodes can be added in real
coupled, optimizing reuse and ensuring flexibility. At run time to meet scale and performance needs. Since each
time, clients have the flexibility needed to couple as closely new node can immediately pull the models and code, it
or loosely as needed and to define the level of autonomy needs from cache, new engines can be deployed quickly
depending on the application, functionality, or need. without needed to configure them for a specific need. Pega’s
managed service offering, Pega Cloud, leverages Docker
Because each Pega engine node (essentially a JVM) caches
containerization to quickly deploy and scale new nodes.
and executes only the functions that it has been asked to,
you can deploy Pega in a highly distributed and loosely We also give you the flexibility to deploy in the style that
coupled way. For example, a collection of Pega nodes can be is best suited for your organization. Whether you’d like to
assigned to run a single piece of AI-driven decision logic as a deploy at set intervals or continuously, our platform lets you
REST service. Those nodes will cache and run only that logic architect and deploy to your business needs.
The flexibility of Pega’s platform ensures its success at serving various organizations’ needs. From large
global institutions like AIG, Allianz, and American Express, to smaller departmental projects or start-ups,
Pega has met the vast and differentiated needs of these organizations with a unified, yet flexible, application
development platform.
www.pega.com | 9
 1 2 3 4 5

Flexible, Automated DevOps Pipeline Flow

ENABILING AGILITY:
3 PEGA FEATURES WITH MICROSERVICES BENEFITS
Development Continuous Integration Continuous Delivery Deployment

AUTOMATED
SERVER
As an organization that has been developing enterprise Pega’s approach to application development has embraced
software for over 30 years, through a number of architecture microservice benefits since long before microservices were
paradigms and trends, Pega has had to balance rapid cool. Pega’s model-driven approach to development is visual,
innovation with the needs of our seasoned customer base. enabling both IT and business stakeholders to develop Unit Tests Packaging Test Ready to ship tests Staging Post deployment tests Production
System of record
environment Regression tests | Performance | Capability
This means our development and IT teams have had to applications visually. Visual models are stored in a repository

PROMOTE
PROMOTE

PUBLISH

PROMOTE

INPUT
innovate and deliver new features quickly to the market that implements a patented algorithm (the Situational Developer

while ensuring that our core capabilities are stable, robust, Layer Cake), allowing reuse of common functionality along
and dependable. As a result, Pega has engineered the with tailored overrides aligned with specific geographical,
Pega Platform to allow our customers ultimate flexibility by functional, or business unit needs. Because business Developer

offering them the ability to choose the best development users and IT professionals can quickly define and deploy
Artifactory Repository
approach for them. applications built in Pega, the platform is often used to drive
rapid application delivery and innovation products, knowing QA

that Pega’s robust foundation will enable them to scale to

QA
transformation projects when needed. UAT Sys Admin

LEGEND

Pega Features PEGA FEATURES RAPID APP DEV Manual Step Manual Feedback Automated Step Automated Feedback Artifact Repository Static Pega7 System
AND CONCEPTS BENEFITS
with Microservices
Benefits DevOps Speed
Componentization Scale
Changes made in Pega can be managed, tested, and In a DevOps model, development is done in a shared source
Technology heterogeneity Safety
and compatibility deployed via a continuous delivery pipeline, leveraging control management environment that is packaged and unit
automated system of tools and processes to quickly and tested, and then sent to an artifact repository for versioning.
Cloud choice
efficiently integrate and test developer changes. The Pega Next, it is moved to a test environment for regression
design environment allows for design time at run time, so testing after which it is promoted to the artifact repository
developers and designers can immediately see the impact of again before being imported to production. All of this is
their changes. Changes and deployments happen in real time done using your existing preferred software in place for
3.1 DevOps rollbacks and changes to the application released as business
and do not require system downtime or restart. Changes are automation, source control management, and testing, such
needs dictate. With continuous integration, developers can
simply migrated to a centralized repository and automatically as Jenkins, Git, Bitbucket, among others. The Pega Platform
Pega’s application development platform supports a release code into a shared repository several times a day to
pulled by any of the nodes that may be impacted. provides open hooks and services based on standards and
DevOps pipeline, which is critical for the development and enable easier error detection and location, and thus leading
is continually expanding our support to the latest Software
As you develop your application on the Pega platform our
deployment of microservices. DevOps combines organization, to quicker problem resolution. Pega has helped PayPal move
Development Lifecycle (SDLC) tools.
DevOps pipeline breaks down barriers between your teams
culture, and technology to ensure that development, quality, to continuous integration and achieve higher quality and an
and is flexible enough to adjust as your needs change.
and operations teams across an organization collaborate accelerated time to market by automating their unit tests,
effectively. A DevOps approach allows for application delivery builds, deployments, and functional tests.
and integration that is continuous, fast and safe with updates,

10 | Delivering Microservices Benefits with Pega www.pega.com | 11

 1 2 3 4 5

3.2 Componentization Componentization is also defined by how these discrete 3.3 Technology Heterogeneity 3.4 Pega Cloud Choice
entities explicitly connect and communicate. Communication and Compatibility
Componentization is the process of breaking down resources with components is by contract, or only done through Pega’s application development platform is architected for
into separate reusable packages that can easily be consumed explicitly defined inputs that result in explicit outputs. Pega The Pega Platform supports a wide range of technologies the cloud. Pega’s cloud Choice capabilities give enterprises
and reused. It is a central feature of microservices, and also a components define a communication contract that then and languages such as Java, JavaScript, HTML and SQL. When the flexibility required for deploying and running mission-
central concept in Pega’s model-driven architecture. defines the explicit data in and out that is unique to that you create a model in Pega, the code that is generated is critical applications in today’s fast-paced app development
business use case or functionality the component deploys. relevant to the type of rule and use case you want created. environment and it supports the evolving DevOps culture
In Pega you can create components that can run by
Components within Pega can be versioned independently. For example, models that define user screens generate that has enabled faster and easier application delivery.
themselves and are self-contained. Each component delivers
The system can select between multiple versions of a HTML and Javascript. Reports and queries may generate SQL.
discrete functionality and value and has few dependencies.
component at runtime, which enables systems to run Pega ensures that we are optimizing and modernizing the Pega Cloud Choice empowers customers building
A Pega component can be an application, a feature within
multiple versions simultaneously for pilot testing or to ensure code within your application. For example, Pega will generate applications on the Pega Platform to choose the right
an application, a function within an application, or any other
backwards compatibility with specific stakeholder systems. SQL that will be compatible with multiple databases or HTML cloud for their needs:
entity you need to discretely define. At the lowest level, a
that is tested across browsers to ensure that the application ƒƒ Pegasystems’ managed cloud platform, Pega
component in Pega is simply a single model of a business Additionally, Pega allows for segmentation of specialized app
performs optimally. When HTML5 was first published in Cloud, is architected for the Pega application
function, such as a decision, a service level or a business functionality across specified JVMs. Classification of nodes
2014, upgrading the Pega Platform automatically meant development platform and offers developers the
process. Individual models or collections of models can allows you to independently scale your application. On Pega
that user screens were now generated in HTML5, enabling fastest time to value when building applications.
be defined as components and then added to other Pega Cloud, auto-scaling helps with load issues and high availability ƒƒ For those desiring a more controlled environment,
organizations to take advantage of new technology without
applications, called by other Pega logic, or accessed via for JVM failure. Pega also supports deployment in a customer-
recoding their applications.
RESTful service calls. managed or partner-managed Cloud that can be
Pega’s technology heterogeneity and compatibility gives run within private clouds or on Infrastructure as a
users the flexibility to deploy on many different hardware Service (IaaS). Pega continues to deliver choice and
flexibility, enabling developers to select their IaaS
and browsers while maintaining the configuration
platform of choice, including Amazon Web Services
experience. The Pega Platform ensures the code generated
Building Components in Pega (AWS), Microsoft Azure or Google Cloud.
is optimized for the JVM, OS, and database we are running in.
Our models and your business logic can remain consistent,
but the engine generates the underlying code to keep The Pega platform provides developers the flexibility
Edit Component: Twitter feed
CL Pega-PSOR-Components | ID twitterfeed RS PegaPSOR:01-01-01
Save Delete Actions 
up with technical standards and using the best practices of choice when it comes to the Cloud to ensure rapid
available in the industry. application development as well as delivery.
Definition Documentation History

PEGA EXCHANGE Lock component Update password Package

Build better solutions, together. Short description

Live Twitter feed

BROWSE APPS & ADD-ONS Publisher

Pegasystems

Set as ‘Express ready’ 

 Download | Package again

Version: 1.0.00 (1/6/2016 3:14PM) Cloud @ Pega | Understanding the options
Installed apps and add-ons
\
Name Ú Version Ú Publisher Ú Status Ú
Browse

PEGA CLOUD CUSTOMER PARTNER

Component rules and data

Cloud Stats 1.2.1 Pegasystems Enabled

MANAGED CLOUD MANAGED CLOUD

– Ruleset Version

Time control 1.4 QuickApps Enabled TwitterFeed  01.01  Include associated data 
Download
 Add new
Pulse PEGA Pulse 1.2.2 Pegasystems Enabled

Smart UI 2.0.1 QuickApps Enabled About Fastest time to value. Maintain ownership behind Expand existing partner
†
Weather 2.1.1 Sun Anywhere Enabled
Prerequisits
Cloud service built specifically firewall. relationships.
Geolocation 1.1.1 Sun Anywhere Enabled

by and for the Pega Platform. Meet unique technical Single service provider:
Install new Application Version

Notifications 1.3.1 Pegasystems Enabled PegaRULES  7.2.1  

 Add application

Component Version
Unfiied single subscription. requirements: 100% implementation to SaaS.
Social  1.1.1  
availability, geographical Out of the box solution
Cancel Done  Add component Enable digital transformation
limitations. provider: BPO.
across business lines: Marketing,
Sales, Service, Industry.

Application Customer/Partner Customer Customer/Partner

Security / Operating system Pega Cloud Customer Partner

Database / Monitoring

Infrastructure Pega Cloud Customer Partner

Supported Cloud Vendor Pega Cloud Amazon Web Service (AWS), Amazon Web Service (AWS),
Microsoft Azure, Google Cloud Microsoft Azure, Google Cloud

12 | Delivering Microservices Benefits with Pega www.pega.com | 13

 1 2 3 4 5

44 4.2 Reuse and Organizational Scale your business as needed. AIG used the Pega platform to

MICROSERVICES ARCHITECTURES – A REALITY CHECK
4.1 Not a “Silver Bullet”
Many development and operations teams are diving in
head first into a microservices architecture without properly
vetting and planning for the impacts. Deployed correctly
microservices deliver a number of benefits, but they are not
a silver bullet, one-size-fits all solution for all organizations,
applications and scenarios. Microservices are fast, scalable
and resilient, but some use cases and environments
demand that this approach be balanced with the benefits
of a slightly more coupled Service Oriented Architecture
(SOA), which provides similar benefits and mitigates some of
the drawbacks, such as the high overhead that comes with
orchestrating and maintaining the coordination of so many
services.
Pega’s breadth of experience in the technology industry
has given us the unique ability to understand a range of
customer needs. From established Fortune 500 companies
to overnight start-up sensations, we’ve helped all our
customers build for the future and build for change. Offering
solutions that meet vastly disparate needs, we understand
the reality most companies face approaching the hottest
trends in application development, like containers,
microservices and the cloud. We know most organizations
are not equipped to start from scratch and build all their
applications in the cloud with thousands of microservices.
Pega understands you and is built to suit your specific needs,
whether that’s building mostly in the cloud with de-coupled
services or only using the cloud and microservices for
specific business needs and apps.
The Pega’s scalable Situational Layer Cake (SLC) approach
rapidly innovate and scale their applications with our unique
architecture approach by creating a core set of functionalities
to application architecture design was created to align with
to be leveraged across the organization while building tailored
your business and its needs. Consistent, reusable, static
functionality to specific regions and business units.
functionality is in the base layer like your company’s policies
and procedures. While the top layers are changing, specialized Whether the business is expanding into new geographies,
functionalities tailored for geographies, products, customer acquiring another firm or scaling in existing territories to meet
types, and business units. customer demand, our architecture enables you to scale your
technical architecture as quickly as your business and market
The benefit of Pega’s SLC architecture design is that each
dynamics demand.
element within the architecture is discrete and operates
as a separate element but durable enough to scale across
Situational Layer Cake
CHANNELS & THINGS

Microservices architectures evolved from the rapid
innovation being done by companies that did not exist 10
to 20 years ago. Innovative “digital natives” like Netflix and
Amazon have built their infrastructure and architecture
around microservices, the cloud, and DevOps. But
established enterprises, which run the vast majority of
their core business processes on legacy systems, simply do
not have the ability to go to a microservice and cloud-only
environment overnight. In fact, most organizations should
not and will not adopt a pure microservice and cloud-based
infrastructure. Those organizations need to think about how
they can build an agile layer that is microservices friendly and
allows for rapid change, while connecting to, and in some
cases, wrapping the legacy environments. Pega Platform
provides a way to deliver microservices benefits while still
connecting the core systems of your business.
Pega has been around for 30 years and we have seen
the evolution of many architectures and tech trends.
Pega future proofs your applications by keeping up with
COMMERICAL APP RETAIL APP
architecture and technology trends and incorporating their
benefits with none of their drawbacks. We keep up with the
trends so you can focus on what’s most important, your SMBs Enterprises Auto Loans Student Loans
business and building successful applications that meet
your needs and those of your customers. Overall Pega is not
constrained by any one architecture approach and focuses
Commercial Lending Real Estate Lending Mortgage Home Equity Loan
on including and delivering only the best benefit amongst all
architectures without any of the drawbacks.
The Pega platform has evolved along the same path as your
engineering teams and that’s why it is uniquely positioned LOAN APPLICATION AND LENDING (PROCESS AND RULES)
to give you the flexibility and resiliency you need when
developing applications. The following sections cover the
ENTERPRISE LAYER (SINGLE SIGN-ON, AUTHORIZATION, COMMON PROCESS AND DATA ACCESS)
additional capabilities the Pega platform offers and go into a
deeper dive on what we have built to help with microservices
and go beyond their capabilities to soften the impact of their
drawbacks.

14 | Delivering Microservices Benefits with Pega www.pega.com | 15


2010s
MICROSERVICES
4.3 From Low Code to No Code
Pega’s model-driven software development goes beyond
low code with an approach that is visual and requires no
Commit
technical coding experience Continuous Integration
and delivers microservice
the syntax of code. The model-driven
benefits with none of the drawbacks. Pega’s architecture is
loosely coupled at design time but can be, as needed, tightly
coupled at run time to deliver an efficient and optimized user
experience. Traditional microservices are largely code-based,
but the future of enterprise software goes beyond code. In
order to align with business and market needs, organizations
Source control management
need to rapidly develop and change applications and
empower non-technical resources to help. Pega’s visual,
PUBLISH
forms that contain the metadata for a specific business use
case they’d like to achieve. The metadata is then turned
into code by Pega, which enables the user developing the
app to focus on the business use case and value versus
Continuous
Delivery
and beyond low code Continuous Deployment
also gives you the ability to reuse critical capabilities
approach means Pega does the hard work keeping up with
new technological trends and best practices as they emerge
for you. Tactical work getting up to speed on the latest trends
and best practices to generate the most optimal code is left
to Pega, giving you all the benefits but no hassle and leaving
you to focus on the strategic business initiatives and goals
Test system image Test
you are measured on. -regression tests
-performance -compatibility
Pega’s model-driven architecture enforced granularity
4.4 Integrations
Pega gives you unmatched flexibility to connect to existing
business-critical apps, services and data sources. Pega
across channels with our mashup technology. With a vast
number of connectors and services that allow for data and
communication to be fed into and out of your application
you have almost limitless flexibility and are not bounded by
select data sources. Our connectors and services enable you
and the enterprise apps you build to have limitless potential.
Production
Pega supports the most widely used connectors such as
HTTP, REST and SOAP to send vital communication and data
1 2 3 4 5
other services to send critical communication and data into
the Pega platform from the same systems. All connectivity
options are quick to setup with zero-code configuration
necessary for standard protocols and transports.
Applications need to manage data more efficiently, especially
in distributed microservices applications. For enterprises that
have a multitude of legacy systems, they need to connect to
and pull data from, this becomes especially critical. Pega Live
Data creates a data virtualization layer separating how your
business apps use data from their plumbing. When you have
multiple systems to connect to, especially legacy systems,
Pega helps you wrap and renew around your existing
systems. Instead of ripping and replacing these systems, we

PROMOTE
model-driven approach (Software that writes your software™)

INPUT
at design time, but does not require the same level of from the Pega Platform to your existing databases, legacy help you seamlessly transition from legacy data, systems and
empowers business stakeholders to innovate. granularity at run time. Instead of trying to figure out the technology to new microservices architecture by wrapping
apps, ERP systems and other business critical apps and
Develop Test Validated Dependent Validated Dependent
The Pega Platform’s model-driven
-unit test approach enables Application optimal runtime before you build your app, Pega lets you
Component services. Pega also supports HTTP, REST and SOAP among and renewing with Pega Live Data.
-critical integration tests repository repository
business and technical stakeholders to quickly develop focus on building the optimal business process and then
functionality and applications visually without code. adjusting the run time to the channels and experiences you
JFROG Extending Legacy Systems with Live Data
UnderstandingArtifactory
complicated coding language is no longer are looking to deliver to your users and customers.
a necessity. In Pega’s model-driven approach, users fill out

App Development in 3 Parts

1 2 3 Your processes
and screens
CASE DATA INTEGRATIONS
The first is building a case model The next part covers the data model Finally the third part covers any integrations
that helps define the business logic, that builds the metadata and the application needs to be able to function
rules and processes. framework for the application. or achieve its business goal.

Each of these three parts can be done by anyone quickly and Finally, Pega’s low code approach does not have the
easily without code. Once the three parts are complete the drawbacks of standard microservices:
Fetch Upon Reference Intelligent Caching Background Retrieval
PEGA
app is live. Application development time is reduced from ƒƒ Complex development, you must carefully handle
LIVE DATA
weeks or months to hours or minutes. requests traveling between modules
ƒƒ Multiple database and transaction management
Taking a closer look at the first part of Pega’s application
development approach, the case-driven structure allows for ƒƒ Each dependent service needs to be confirmed
before you can start testing
users to have a lot of advantages over traditional coding.
®® With Pega you can easily track and discover
Users can build many small cases with logic for each case Systems of record
potential reuse candidates with our provided
being broken up into independent components. Additionally, and big data
documentation and reporting that helps easily
case processing occurs with API actions. Further, cases can
track services and monitor interdependencies
spin off other cases, passing required data to a new case.
between services
®® Additionally Pega provides easy automation
automation

16 | Delivering Microservices Benefits with Pega www.pega.com | 17


Pega Live Data lets you define data in business terms like
customer, product, and details while developers can declare
how the data is mapped to objects and how the data is
accessed and cached. Additionally, they can import data
definitions and define multiple data sources for each data
object, allowing your application to have a single view of
your business data even if your data is coming from multiple
systems.
When accessing data, your application simply references
the live data object and live data will access the data from
the correct source or retrieve it from cache. Live data can
also predict the data that you will need and pre-fetch it
for you. Live data is scalable and can be used across the
organization. The live data objects can be used by different
parts of the organization and select the right data sources
for each situation.
Integrators and Connectors
18 | Delivering Microservices Benefits with Pega
1 2 3 4
Pega also gives you the ability to reuse critical capabilities
across customer channels with our mashup technology.
Instead of using thousands of services and processes
to ensure a seamless and consistent experience across
customer channels, Pega enables you to do it much
more efficiently. Pega mashup lets customers put Pega’s
responsive UI directly into your website or mobile app. The
Pega UI lets you reuse and embed a specific process, case
management and decisioning capabilities across channels,
so your customers have a seamless, continuous and
consistent experience across channels.
5 1 2 3 4 5
5 SUMMARY
As Agile and DevOps cultures spread across organizations Innovative, forward-looking enterprises, like the one just
and cloud adoption accelerates, more and more described, know that rapid app development can be achieved
organizations are adopting digital transformation strategies. by adopting and incorporating, as needed, microservices,
As a result, corporations are focusing on rapid app DevOps deployments and business friendly visual app dev
development and ensuring they can innovate and transform approaches. These companies know that a one-size fits-all
faster to ensure they keep their competitive edge. approach is not going to lead to success. They know they
have to tailor their application development strategy to their
One of our clients, operating in the financial industry, was
business needs, and do not want a cookie cutter approach
looking to re-architect their existing set of applications and
to pigeon hole their application architecture or development
achieve microservices benefits as well as specifically to:
approach to the hottest industry trends.
ƒƒ Gain more granular control over their release and
lifecycle management
ƒƒ Lower application risk
ƒƒ Release more granular features to market The Pega Platform helps organizations incorporate
and balance best-in-class technical approaches
ƒƒ Enable easier planning and ownership
that are best-suited for their business needs.
The Pega platform enabled them to meet their goals and Pega gives companies the technical flexibility and
requirements with the ability to build small cases around scalability that helps growing enterprise rapidly
discrete functionality. Pega also allowed for the logic in each develop, transform, innovate and meet market
case to be built into independent components, allowing demands with unprecedented speed and agility,
for more granular control over features and functionality. helping them pull ahead of their competition.
Additionally, cases can pass data to new cases that are spun
off operationalizing and streamlining the data flow. Finally,
Pega gives them the visibility they need with Pega’s reporting
and dashboards to track a given object like a loan application
across the different cases it traverses, across the entire
loan application process, through pre-qualification, filing,
processing, review etc.
www.pega.com | 19
ABOUT PEGASYSTEMS

Pegasystems develops strategic applications for sales, marketing, service and operations. Pega’s applications
streamline critical business operations, connect enterprises to their customers seamlessly in real-time across
channels, and adapt to meet rapidly changing requirements. Pega’s Global 500 customers include the world’s
largest and most sophisticated enterprises. Pega’s applications, available in the cloud or on-premises, are built on
its unified Pega 7 platform, which uses visual tools to easily extend and change applications to meet clients’ strategic
business needs. Pega’s clients report that Pega gives them the fastest time to value, extremely rapid deployment,
efficient re-use and global scale.

For more information, please visit us at WWW.PEGA.COM

© 2017 Pegasystems, Inc. All rights reserved. All trademarks are the property of their respective owners.