PEGA docker container 1

How to  run a PEGA application server in docker container -

Successful Project Delivery

Successful Project Delivery  shouldn't stop at releasing the code to production and getting signoff . After the release we should continuously monitor the usage and follow the below cycle until the usage is optimized/100% utilization is achieved

Code release to production-> get usage /Success metrics based on use case  -> Analyze the metrics -> outcome leads 2 options 1. Training opportunity   and 2 . enrich your  user story and implement it-> release the enriched code.(Step 1 in the Cycle)

This logic should applied to every use case and you see the benefit /satisfaction for your work.

Performance

 NFR - Non functional requirements are critical data points which should be captured part of Requirement Gathering .

Dedicated Performance  team preferred depending on the complexity and size of applications.

JDBC connection pool VS DB link connection pool

Java source  Application  connection pool VS DB link connection pool

Application connects to one database and that data base has a DB link to another database where the required data resides.

This is not optimized approach but could be scenario- DB link connection pool is one parameter need to be considered in the  design

Security:

The below 2 statements were  found interesting to me while I was reading the pega LSA course 

"Obfuscation of URLs is not a guarantee that an attacker will never find way to form a URL "

"Obscurity is not security"

bottom-line is , define the  authorization policy that explicitly prevents the unauthorized access. 

-------------------------------------------------------------------------------------------------------------------

Security: Reports and attachments

How to define the Authorization policy for the delegated customer created reports?