Nathan,
Probably should start a different thread for this since I am guessing
Shannon won't have another platform in mind as he develops, but....
"..cross-platform capability.Sounds good in theory, but for small
companies, it's a really good way to overextend one's resources"
I wonder how much experience you have had in this arena, directly, since
I would guess that 99% of your development is in RPG (unless there is
something new in your toolbag!). I find there is exactly no effort in
developing an application that runs on multiple platforms vs IBM i when
written as a Java servlet. In fact, I write most of my applications for
DB2 on i5/OS and have deployed to both Linux and Windows without so much
as a stumble. I would guess a PHP application could fall into the same
category.
I would guess my substitute dispatching and absence management system
could be considered "narrowly scoped" but something like Sugar CRM?
Runs on Windows, Linux and i without so much as a difference in a line
of code (to my knowledge). I would guess just defining database
connections during configuration time is about all it takes.
Writing an application that runs on multiple platforms for a large or a
small company seems to be a fairly prudent approach. I know there are
some might not consider Java or PHP to be a "business language" but
there are plenty of what I would call fairly robust business
applications written in PHP and Java.
The best part about writing in Java, for me at least, is that even
though my database access revolves around DB2 for i5/OS, I can import
the physical files and data into MySQL, or Derby or MSSQL and use them
as a test bed for my applications. Makes writing and testing code for
the IBM i database easy at 30,000 feet as well.
My 2 cents...
Pete
Nathan Andelin wrote:
From: Shannon ODonnell
The subject line of the email sums up the question:
My inclination would be to run benchmark queries and updates against both. I give quite a bit of weight to performance.
I don't give much weight to cross-platform capability. Sounds good in theory, but for small companies, it's a really good way to overextend one's resources - unless the application is narrowly scoped.
midrange.com
