We have requirement that we have application (ABC)which is built on HTML and back end SCALA(all validation logic is in SCALA). Client wants to put the validaiton logic in PEGA application (get rid of SCALA from ) but in existing application , on every on change the ABC sending request to SCALA rule engine and that engine responding lighting FAST response. If we want to design this in PEGA then one solution is using REST-Service integration rules, but I doubt whether will it handle each on change event response when (about 2000 users are playing with 300 and more ui fields in ABC application).
Can we cache the Pega rules in XML format or in any other format where other application can use it other container JVM , so that ABC application can talk to pega application which is cached version deployed in same container where ABC applicaiton deployed.
Can anyone worked on such design approach.
***Edited by moderator, Maryrita: moved to Product Support from Applications***