I would like to share our
Aptana Cloud experience, after two months of use (or misuse), building a financial application
ConPA, an advisory application focused on the optimization of the
asset allocation.
OverviewThe customer builds a basket of assets, selecting the assets directly from
Yahoo Finance, and gets an optimal portfolio, the optimal weights of the assets. A performance chart of the portfolio since a reference date (if it's different from today) and a pie chart are displayed. You could check if your portfolio is efficient. :)
In the custom release, the financial information (the catalog of the products, the time series of prices, etc.) will be stored in the MySQL instance of the Cloud and not retrieved from the net.
The frontend is developed using the JavaScript (what else?)
Yahoo! User Interface (YUI). We will use YUI also on server side.
In the backend there is our math engine, an optimizer translated from Fortran to JavaScript, modified to resolve the problems of the portfolio asset allocation. We don't note any performance degrade compared with Fortran release run on local machine (Core 2 Duo Processor 2 GHz): of course, there is the overhead of the callbacks (retrieving the historical prices from Yahoo, for instance), but the rendering of a Flash chart is slower than the optimization phase.
Development configuration-
Eclipse 3.4
-
Aptana Studio plugin 1.2.x
-
Subclipse 1.4.3
-
Firefox 3.0.1 +
Firebug 1.2.0b12
Development notesFortunately we can concentrate more on the business code, the process of the asset allocation, than on system issues. The sync with the Cloud and with SVN server is painless, but a bit slow, from Italy, using often a mobile connection. We work at office and at home: the team work is a breeze and the message center helps.
We have integrated
JSLint as external tool in Eclipse, using cscript, because we need the latest release and we need some control with the validation options. The outline view (Ctrl+O) is quite used to find the code we are working on. Another shourtcut we use often is Ctrl+Shift+R to open a resource.
We don't use very often the preview and we debug the client side in Firefox with Firebug. The Tail View helps, because we can check any error server side quite fastly. Sincerely we debug the server side code as client side code, commenting out the Jaxer callbacks for a while. Not so efficient, we know, but we should take confidence with the
Aptana Studio debug environment.
We check the figures with
R framework, a free software environment for statistical computing and graphics.
All the code, frontend and backend, is about 50Kb.
ConclusionSo we are satisfied about the integration with the
development tool and the
facility infrastructure. Obviously there are some glitches, due to beta level of the Cloud (and our app), but no show stoppers for us (until now). :)
The Cloud experience has been positive and we will continue to develop our business with this technology and service.