What about using hibernate with BMP entity? Does it provide good performance?
Originally posted by Ajith Kallambella:
"Is this the right architecture" is like asking "Is this the right car"? If you do not qualify your question with requirements, motivation(to move to a new architecture), and other expected outcomes in measurable terms, you will only get opinions. As technologists, we need to worry first about the business problems we are trying to solve, and *then* the right technical solution to balance the priorities. For example, if you had included in your requirements "a highly dynamic web page with an average response time of 10s", then AJAX would qualify as an option. OTOH, if you had said "one of the limitations is limited network bandwidth", then we would be forced to think alternatives to AJAX.
Everything you have( and others too) have listed - Hibernate, AJAX, iBatis,JDOM, Spring etc. are simply *tools* to help you achieve what you want to. But without knowing what is that you want to achieve, we'll just be blurting out words and acronyms. Whether EJB or not, iBatis or Hibernate, JSP or JSF, IoC or lookups - are all petty issues. Focus on the big picture. Tell us more about the business problems you are trying to solve and then we'll help you figure the *options* for the right architecture.
Originally posted by Vicky Pandya:
You seemed to miss "Trading software system" in my first post. Trading is a world known business and you should have an idea about the business reqs.