Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Rick Scotson (RickS310) Healthfirst
Healthfirst
RickS310 Member since 2015 1 post
Healthfirst
Posted: Oct 24, 2016
Last activity: Nov 4, 2016
Posted: 24 Oct 2016 14:26 EDT
Last activity: 4 Nov 2016 11:25 EDT
Closed

Architecting a Pega application based on microservices to facilitate DevOps realization

Are there any issues with architecting a Pega application this way, breaking it into fine-grained loosely coupled components with a bounded context (so cohesive)?

Assuming this is supported, are there any limitations re cloud-based deployment of individual microservices?

To see attachments, please log in.
Installation and Deployment

Posted: 7 years ago
Posted: 27 Oct 2016 12:56 EDT
Frank Apap (APAPF) PEGA Senior Director, Launchpad Provider Success
Pegasystems Inc.
US

There are no issues in breaking up an application into fine grained services that have  a clear and singular focus, in fact this approach is a great way of realizing DevOp benefits through improved testing capabilities and reduced defects caused by unexpected dependencies.

To see attachments, please log in.

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

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice