RE: Using JAVA for core business logic - Good/Bad?

Joe Pluta wrote:
When I address this issue, I consider one question to be the most
important: do you plan on leaving your DATABASE on the System i? If
not, then all bets are off...

Joe,

I believe the intent is to replace the System I. There was a recent
project to locate a suitable replacement. The result being that one was
found but the cost were prohibitive to make the move at this time. The
replacement was a mainframe package that we would be using in a
timeshare fashion if I understand correctly. We wouldn't be purchasing
a mainframe. So, to answer your database question, today, yes we are on
the System I, but maybe not tomorrow. A question I want to ask is if we
were going to move to a mainframe because of our size (supposedly one of
the projects findings) then why are we in such a hurry to get rid of the
System I when it is doing the job size wise for us now? AFAIK, there
are no performance issues. Just issues with code written prior to 1992,
but we won't go there.

I have been advocating for change and modernization of our application,
I'm just not convinced that JAVA is the way to go. At least not in the
manner presented by our architecture group. That's what prompted the
question. I think I would recognize JAVA code if I see it but that's
about the extent of my JAVA knowledge. I don't want my lack of
understanding to get in the way of backing the 'best' way to move
forward.

Rick

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.