Re: Why would you use MySQL with PHP instead of the native DB2 with PHP on iSeries

You state a great reason for selling an i, if the customer doesn't already have a "business computing platform".

However, when I do install into an "existing account" where the "business computer platform" is Windows Server 2003 and the DB is MS SQL server (for example) they have hopefully already invested in those things. In other words, the assumption is that if they are insisting on an application that runs on Windows Server 2003 they already have other applications that run on the platform and they have the infrastructure and expertise to have your list covered. I work primarily with school districts and yes, they have plans, expertise and infrastructure to meet the items on the list. Usually I don't have to do much more than to verify those things on your list.

However, if they are on Windows Server and DO need those services, provision can be made for them, at an extra cost of course.

Pete

Nathan Andelin wrote:

From: Pete Helgren
Java, so far, with JDBC, has been very easy to move from
platform to platform with.

It's one thing to find a compatible runtime for an application, but what about:

- deployment scripts (the software that installs, sets up, and configures your runtime environment)
- setting up journaling (or it's equivalent) on every platform
- backup procedures
- restore procedures
- disaster recovery procedures
- reporting
- batch procedures
- ftp procedures
- email integration
- Windows user's demanding authentication against Active Directory, while Linux & IBM i needing another
- OS upgrades
- Hardware issues
- Performance tuning
- Database repairs

That's probably a short list. Each platform has a different set of issues. Under IBM i you're dealing with QZDASOINIT jobs. On another platform it would be different. Do you want to be in a position to provide full service support? Or is that the customer's problem?