måndagen den 11 november 2002 kl 16.07 skrev Eric Kaplan:
We have an application that is used by portfolio managers to manage money.<snip>
They manage one or more portfolios, where a portfolio consists of one or
more positions. Each position corresponds to an asset (a given asset can be
associated with multiple positions), and the asset is associated with
pricing information. So, it's like:
Portfolio----<Position>-------Asset-------Valuation
Depending on how many managers doing how many portfolio valuations per hour - will let You know how to design. Since You are going to read in the data and act upon it without transactions - right ? You are going to do a valuation of assets at a historic date in time ... You are not going to change/manipulate the historic data-feed data, therefore I would go with a O/R mapping tool that will help in translating the data to objects (75% of the work really) and work upon that object-DB - cache what is possible ... hopefully Your "assets" is only in one market, in my experience the hard part was to calculate the many index for all different market holiday rules to get the correct valuation ... the speed was not really a issue for us since the system was batch oriented ...
/peter_f
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
