• Post Reply Bookmark Topic Watch Topic
  • New Topic

Design Issue for a product  RSS feed

 
sandy gupta
Ranch Hand
Posts: 228
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there People,
We are in the transition phase of our product from a Java,CORBA based system to one on J2EE using xml,jms etc.
First a li'l bout the product: It is a product that will be used in the telecom industry to provision services like cable, phone activation for the user and there are expectedly 7-12K users for the product. We are expecting 1500-2000 simultaneous logins. Now the issue here is that the CORBA objects are already existing(as point solutions for the services) and the front end is a browser based applet (that is downloaded at the client side); So should we go for a totally revamped system that has no Corba in it or shud we go for the existing Java Corba Objects integrated as legacy objects into our new model.
The only thing we are looking for in the new system is Performance Gain.
What i proposed is that we should go for a system that uses an App Server to give the front end & a part of the business logic. Using a facade design pattern, generate the object that have reference to the existing CORBA Objects and use those to implement the point solutions. We also propose to use the XML as a messaging solution coz that wud help in making the product more scalable and for furthur additions to the system.
I would like to know the opinion of all the brilliant people who come to this forum.
Bye
Sahil
 
Athar Javaid
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sahil:
With 2000 simultaneous users and expectations for big boost in poerformance, I would keep it simple if possible - J2EE all the way. This may be the right time to bite the bullet - do away with CORBA and JAVA objects. Pay attention to development costs and application life cycle.
AJ
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!