This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
i have to develop a web application managing statistical data. The amount of data is counted in one hundred million lines of numbers. The objective is to display html pages within some tables, charts and maps. These pages would be generated on the fly. Data used in these pages could be computed (formula) using others data (like ratio, evolution, percentage ...). There is a formula for each displayed information. The data is stored in database, of course. One of the objective is to allow the final user update data and add data into the database. Then this information could be used into the formula from the final html pages. These new data are negligible in quantity but they are an important functionality.
Well...my questions are simple... is j2ee the framework to build that? what kind of api i have to use? EJB are too low, memory consumer? ORM? ORM with JPA? using EJB for the business layer? MySql, Oracle or PostgreSql? Just a single MVC framework, struts or jsf? using RIA (javafx) or just simple Htpp application is enough? well.... i really dont know how to begin, what tools use, how to measure and anticipate the performance.... if you have any information, way to guide me, web ressources, books, idea of implementing this...you are welcome thak you !
I'd say the choice of web framework is secondary to getting the database queries to perform well. Any of the DBs you mention will probably do, but getting the table design, indexes and queries right could take a bit of time.
I don't see where JavaFX would particularly help with any of this.
Ejb is costly and it depends the application server you are using and based on the requirement. If you are trying with your own interest, you can go for Spring - ORM(Hibernate/iBatis). Displaying millions of record is not a problem if you follow 1) Implement the pagination concept in ORM level 2) Fetch values on click of every 'next>>'
Hope you got some idea!
Joined: Sep 11, 2007
data are not just displayed in a html table; they can be displayed as charts or maps. So sometimes one hundred of numbers can be used to produced just one element on the html page. If the ORM (with Hibernate) is used, there will have one hundred of instances of a NumberData class built/requested from a ejb stateless.
Computing can be done between sets of data. this is a very time consuming process like generating chart and maps, so that's why JavaFX can be used : the client is computing and the server is just use to provide data via http requests.
well, i'm very confused about this. i think our task is not the classic web application with customers, vendors...