Jay,<br><br>Here is my 2 cents: If you are intending to replace Perl with Java then consider Groovy instead of Java. Groovy has a lot of the benefits of Perl (Dynamic Language), but runs on the JVM and can interface with class files that were created with javac.<br>
<br>Let us know what you decide.<br>-- <br>Michael Potter<br><br><div class="gmail_quote">On Mon, Jun 1, 2009 at 12:14 PM, Jay Strauss <span dir="ltr"><<a href="mailto:me@heyjay.com">me@heyjay.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi all, need some advice.<br>
<br>
I want to build a new system. My bro and I have a small<br>
equity/options trading application. We cobbled it together in Perl<br>
and Oracle years ago. Things have broken, some of the stuff we want<br>
to change. Ultimately we want to start over.<br>
<br>
I'm just trying to decide on what architecture to use going forward.<br>
I know this is a pretty wide question.<br>
<br>
Most (all) of the processes will run on a single box. I don't really<br>
have an idea of which presentation route we'll go (full rich client<br>
maybe using Java/Swing, maybe a Java Script client using GWT, maybe<br>
plain HTML). The client will probably request functionality from the<br>
server.<br>
<br>
I was thinking we'd do the whole API for asking for quotes, requesting<br>
analytics, inserting transactins... via HTTP (SOAP).<br>
<br>
Can anyone give me their thoughts on their lessons learned, maybe<br>
routes to try, stuff I should be thinking of...<br>
<br>
(again I know this is pretty open ended, but I'm interested in what<br>
others have done with success)<br>
<br>
Thanks<br>
Jay<br>
_______________________________________________<br>
Chicago-talk mailing list<br>
<a href="mailto:Chicago-talk@pm.org">Chicago-talk@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/chicago-talk" target="_blank">http://mail.pm.org/mailman/listinfo/chicago-talk</a><br>
</blockquote></div><br>