On 11/3/2015 4:01 PM, Rob wrote:
I may be wrong to want all of my business logic in PHP...
Here is the conundrum that we face. I think it's germane to this
discussion.
We have thousands of RPG programs, display files, printer files, etc.
They run every day, doing the work of the business.
The business rules are therefore in these programs.
We'd like to extend some new functionality via a web interface.
If we were to put some business rules on the web side, we'd now need to
make sure that the web team would need to communicate all of their
changes to us, and vice versa - there'd be two teams maintaining two
sets of business rules. Eventually, one team would neglect to tell the
other about a minor change, and the database would start to come apart
due to lack of integrity.
We'd love to simply expose all of the business rules as stored
procedures and UDFs but the decades of development that went into the
RPG code doesn't make it all that simple to separate out the rules from
the database I/O from the presentation I/O.
I've never heard a simple solution to this dilemma. How will your group
handle it? Or did I completely misunderstand, and your situation is a
greenfield project so you don't have any existing business rules to
worry about?
midrange.com
