D
dbeavon
Guest
I now have a couple of months experience using PASOE. I see that Progress deserves a lot of credit for integrating its appserver technology into Apache Tomcat. Many of the new features of PASOE are available because of the Tomcat platform itself. I found a pretty good presentation of the benefits of PASOE as compared to "classic appserver": http://pugchallenge.org/downloads2015/433_Migrating_to_PASOE.pptx As-of now, we don't see ourselves using the other new transports yet (REST, SOAP), and will probably stick with APSV for a year or two. Given that we will use APSV, I'm trying to determine if there is still a compelling reason to use PASOE instead of classic appserver, given that there will be additional cost. I've been focusing primarily on innovations that Progress has introduced into their own "MS-AGENT" in PASOE, rather than the many improvements they've realized as a result of using the tomcat platform. Most of the "MS-AGENT" innovations can be found in the powerpoint presentation above, starting on page 15 ("Architecture: Multi-Session Agent"). They are as follows: Multi-threaded agent Faster and optimizes resources (Runs same ABL application and client load with less memory and CPU consumption) Improved self-service database access to the OE RDBMS Ostensibly allows session-managed *and* session-free in the same MS-AGENT, but that didn't end up working in practice, so we created isolated "ABL Applications" in the tomcat instance Am I overlooking any other significant innovations in the "MS-AGENT" itself? Outside of the MS-AGENT, I can also identify some other general benefits that will be realized, even for legacy APSV-based applications: New development tooling (integration with PDSOE) New management tooling (REST and JMX) Architected for secure operation (Spring Security Framework included) Scalable (load balancing - available for 11.7.2 and up) Uses less system resources This is the list of innovations that would impact our legacy APSV applications. There are some that are found inside the "MS-AGENT" and others that are outside (part of Tomcat, PDSOE, Progress OE Manager Webapp, etc). It would be helpful to hear if I overlooked anything. We are in the process of trying to evaluate the cost/benefits of using PASOE instead of "classic appserver". I think PASOE is appealing, and has many features that classic appserver should have introduced by now - if Progress had continued to invest in it over the years. I think we've been using classic appserver for 15-20 years... for nostalgia sake I was recently reading the OE 9.1E docs for "classic appserver". It is very applicable today, even when using OE 11.6. (I think the OE 9.1E docs omit information about out some of the stuff about session-free/state-free, but other than that, they accurately reflect the "classic appserver" product as it works today.)
Continue reading...
Continue reading...