db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From t...@apache.org
Subject cvs commit: db-ojb/xdocs faq.xml
Date Sun, 29 Jun 2003 12:11:30 GMT
thma        2003/06/29 05:11:30

  Modified:    xdocs    faq.xml
  Log:
  moved refernces to a separate page
  
  Revision  Changes    Path
  1.25      +3 -109    db-ojb/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/faq.xml,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- faq.xml	22 Jun 2003 20:50:14 -0000	1.24
  +++ faq.xml	29 Jun 2003 12:11:30 -0000	1.25
  @@ -293,116 +293,10 @@
   		OJB is also the persistence layer of choice in several books on
   		programming J2EE based enterprise business systems.
   		(see <a href="links.html">our links and references section</a>)<br/><br/>
  -    </p>
  -    <p><b>Here are some links to projects using OJB:</b></p>
  -    <p>
  -    	<a href="http://www.openemed.org/">The OpenEMed project</a>
  -    	<br/>
  -    	<a href="http://www.ebi.ac.uk/intact/">The IntAct project</a>
  -    </p>
  -	<p><b>Here are some user testimonials from the user mailing list:</b></p>
  -	<p>
  -		"We're using OJB in two production applications at the Northwest Alliance
  -		for Computational Science and Engineering (NACSE).  One is a data mining
  -		toolset, and the other is a massive National Science Foundation project
  -		that involves huge amounts of data, and about 20 or 25 universities and
  -		research groups like mine.<br/>
  -
  -		In fact, I've begun making OJB sort of a de-facto standard for NACSE
  -		java/database development.  I've thrown out EJB's for the most part and
  -		I've tried JDO from Castor, but I'm sticking with OJB. Maybe we'll
  -		reconsider JDO when the OJB implementation is more complete."
  -	</p>
  -	<p>
  -		"We are planning a November 2003 production deployment with OJB and WE LOVE
  -		IT!!  We have been in development on a very data-centric application in the
  -		power industry for about 5 months now and OJB has undoubtedly saved us
  -		countless hours of development time.  We have received benefits in the
  -		following areas:<br/>
  -
  -		-> Easily adapts to any data model that we've thrown at it.  No problems
  -		mapping tables with compound keys, tables mapping polymorphic relationships,
  -		identity columns, etc.<br/>
  -
  -		-> Seemlesly switches between target DB platforms.  We develop and unit test
  -		on our local workstations with HSQLDB and PostgreSQL, and deploy to DB2
  -		using the Type 4 JDBC driver from IBM.  Works great!<br/>
  -
  -		-> Makes querying a breeze with the PersistenceBroker API<br/>
  -
  -		Overall we have found OJB to be very stable (and we've really tested it out
  -		quite a bit).  The only issues we've got outstanding at the moment is
  -		support for connections to multiple databases, but I've noticed in CVS that
  -		the OJB guys are already fixing this for OJB 0.9.9."
  -	</p>
  -
  -	<p>
  -		"We've been using it in "production" for a long time now, from about
  -		version 0.9.4, I believe.  It has been very robust.  We don't use all of
  -		its features.   We've only see to failures of our persistent store in
  -		about 9 months, and I'm not sure they were due to OJB."
  -	</p>
  -
  -	<p>
  -		"So yes, we have made a quite useful mediumsized production website
  -		based on OJB (with JBoss, Jakarta Jetspeed, Jakarta Turbine
  -		and Jakarta Jelly, three Tomcats, OpenSymhony OSCache and for
  -		the database MSSQL server, all running on Win2000.)
  -		It is attracting between 600 and 9000 (peak) users a day,
  -		and runs smoothly for extended periods of time.
  -		And no, I can not actually show you the wonders of the editorial
  -		interface of the content management system, because it is
  -		hidden behind a firewall. <br/><br/>
  -
  -		I feel OJB is quite useful in production, but you certainly
  -		have to know what you are doing and what you are trying
  -		to achieve with it. And there have been some tricky aspects,
  -		but these could be solved by simple workarounds and small hacks.
  -		<br/><br/>
  -
  -		The main thing about OJB is that AFAIK it has an overall clean
  -		design, and it far beats making your own database abstraction
  -		layer and object/relational mapper. We certainly do not use all
  -		of it, only the Persistence Broker parts, so there was less to
  -		learn. We love the virtual proxy and collection proxy concepts,
  -		the criteria objects for building queries, and the nice little
  -		hidden features that you find when you start to learn the system."
  -	</p>
  -
  -	<p>
  -		"My Company is building medium to large scale, mission critical
  -		applications (100 - 5.000 concurrent users) for our customers.
  -		Our largest customer is KarstadtQuelle, Europes largest retail company.
  -		The next big system that will go in production (in June) is the new
  -		logistics system for the stationary logistics of Karstadt.<br/>
  -
  -		Of course we are using OJB in those Systems!
  -		We have several OJB based systems now in production for over a year.
  -		We never had any OJB related problems in production.<br/>
  -
  -		Most problems we faced during development were related to the
  -		learning curve developers had to face who were new to O/R mapping."
  -	</p>
  -	
  -	<p>
  -		"I've also worked with OJB on high-load situations in J2EE environments. 
  -		We're using JRun and/or Orion with OJB in a clustered/distributed
  -		environment. This is a National Science Foundation project called the
  -		Network for Earthquake Engineering Simulation (NEES).<br/>
   		
  -		The only major problem that we ran into was the cache.  JCS just isn't
  -		good, and hasn't seemed to get much better over the last year.  We ended
  -		up plugging in Tangosol's Coherence Clustered Cache into the system.  We
  -		can also do write-behinds, and buffered data caching that is queued for
  -		transaction.  That's important to us because we're dealing with very
  -		expensive scientific data that _can't_ get lost if a db goes down. Some
  -		of these Tsunami experiments can get pretty expensive.<br/>
  -		
  -		Otherwise, we use mostly the PersistenceBroker, and a little of the
  -		ODMG.  Performance seems better on PB, but less functional.  It's not
  -		really that much of a problem anyway, because we can cheaply and quickly
  -		add app-servers to the cluster."
  -	</p>
  +		Reference projects and user testimonials are listed 
  +		<a href="references.html">here.</a>
  +    </p>
   
       </subsection>
   
  
  
  

Mime
View raw message