ODBC/JDBC/ORM are not cornerstones of PHP MVC frameworks in any way. MVC frameworks don't care how you get our data, one of the main purposes of MVC is to separate your presentation code from your backend code. Typically your mapper would just call an API end point instead of issuing a direct DB call - the rest of your code would remain the same.
You are correct in that REST web services can be an alternative to direct DB calls such as ODBC/JDBC/ORM. However I don't follow how if someone is considering PHP web frameworks, they may be thinking of doing too much in PHP.
-----Original Message-----
From: Nathan Andelin <nandelin@xxxxxxxxx>
Sent: Tuesday, June 19, 2018 6:05 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] Frameworks
I'll post a link to an ITJUNGLE article that triggered a couple of substantive discussions on Linkedin:
https://www.itjungle.com/2018/05/07/keep-your-ibm-i-baby-not-the-bathwater/
It delineates one company's transition from green screens to PHP-based web applications that interface with an RPG-back-end via some type of API that wasn't specified in the article, but could have been REST web services APIs.
One of the owners of the company, King Harrison IV advocated for this type of architecture on Linkedin.
I view IBM i REST web services as an alternative to ODBC/JDBC/ORM interfaces that tend to be a cornerstone of PHP MVC frameworks. If you decide on a REST web service API, the "model" in MVC effectively moves to the web service, which suggests limiting PHP to the "view" in MVC.
I think this suggest that if you're considering PHP web frameworks, then you may be thinking of doing too much in PHP.
midrange.com
