My first concern is how to best optimize the server for PHP.
Zend and IBM have collaborated to provide an "optimized" runtime
environment for PHP on IBM i on Power. It involves a "Fast CGI" connector
which runs under the Apache based HTTP server, which forwards "requests" to
Zend's PHP Server which runs in a JOB which is running the PASE environment.
The communication flow might be depicted as:
Browser <==> Apache HTTP Server <==> Fast CGI Connector <==> Zend PHP
Server <==> DB Interfaces
I have never seen any benchmarks comparing the performance of PHP on Linux
vs. IBM i. But if Java benchmarks are an indicator, you should see better
performance per core if you compare IBM i on Power vs. Linux on Intel.
All RPG will eventually go away.
That sounds short-sited from an architectural and performance perspective.
If you're concerned about RPG readability, and just general unfamiliarity
with the language, maybe you should consider converting the code base to
free-form.
I have learned there are many debates surrounding the AS400.
You've piqued my curiosity. What sort of debates?
I want my PHP via MySQLi to run as fast as RPG.
That's kind of like wanting a domesticated house cat to run as fast as a
cheetah - it ain't going to happen. How about reconsidering the pairing of
PHP with RPG stored procedures?
Another direction you might consider is to move data validation and
business rules behind DB triggers, using RPG-based DB "event handlers" such
as the following:
http://code.midrange.com/ee85fb606a.html
From both an architectural and performance perspective, it makes sense to
place such logic "in the DB" as opposed to "in the App".
midrange.com
