[Chicago-talk] New system architecture
michael at potter.name
Mon Jun 1 10:35:22 PDT 2009
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.
Let us know what you decide.
On Mon, Jun 1, 2009 at 12:14 PM, Jay Strauss <me at heyjay.com> wrote:
> Hi all, need some advice.
> I want to build a new system. My bro and I have a small
> equity/options trading application. We cobbled it together in Perl
> and Oracle years ago. Things have broken, some of the stuff we want
> to change. Ultimately we want to start over.
> I'm just trying to decide on what architecture to use going forward.
> I know this is a pretty wide question.
> Most (all) of the processes will run on a single box. I don't really
> have an idea of which presentation route we'll go (full rich client
> maybe using Java/Swing, maybe a Java Script client using GWT, maybe
> plain HTML). The client will probably request functionality from the
> I was thinking we'd do the whole API for asking for quotes, requesting
> analytics, inserting transactins... via HTTP (SOAP).
> Can anyone give me their thoughts on their lessons learned, maybe
> routes to try, stuff I should be thinking of...
> (again I know this is pretty open ended, but I'm interested in what
> others have done with success)
> Chicago-talk mailing list
> Chicago-talk at pm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Chicago-talk