You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by th...@apache.org on 2003/06/05 08:04:10 UTC

cvs commit: db-ojb/xdocs faq.xml

thma        2003/06/04 23:04:09

  Modified:    xdocs    faq.xml
  Log:
  add a new section "is OJB ready for production environments?"
  
  Revision  Changes    Path
  1.18      +111 -1    db-ojb/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/db-ojb/xdocs/faq.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- faq.xml	15 May 2003 08:01:38 -0000	1.17
  +++ faq.xml	5 Jun 2003 06:04:09 -0000	1.18
  @@ -19,7 +19,7 @@
       <li><a href="#18">Where can I learn more about Object/Relational mapping in general?</a></li>
       <li><a href="#34">How OJB performance compares to native JDBC programming?</a></li>
       <li><a href="#35">How OJB performance compares to other O/R mapping tools?</a></li>
  -
  +    <li><a href="#Is OJB ready for production environments?">Is OJB ready for production environments?</a></li>
     </ul>
   
     <p><b>Getting started</b></p>
  @@ -265,6 +265,116 @@
       </p>
       </subsection>
   
  +    <subsection name="Is OJB ready for production environments?">
  +    <p>
  +		Depends on your production environment. If you want to program an aeroplane autopilot
  +		system you should not use Java at all. (according to the official disclaimer).<br/><br/>
  +
  +		But I assume we are talking about enterprise business applications, aren't we?
  +		And for such applications it's a clear <b>yes</b>.
  +		OJB is used in production application since version 0.5.
  +		We have about 6.000 downloads each month (and growing) and a large user base using it in a wide
  +		spectrum of production scenarios.<br/><br/>
  +
  +		We provide a regression test suite for Quality Assurance. You can use this testsuite to check if
  +		OJB works smoothly in your target environment.
  +		(see <a href="platforms.html">supported platforms documentation</a>)<br/><br/>
  +
  +		We also provide a performance testsuite that compares OJB performance against native JDBC.
  +		This test will give you an impression of the performance impact OJB will have in your target
  +		environment.
  +		(see <a href="performance.html">Performance testsuite documentation</a>)<br/><br/>
  +
  +		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 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 releated 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>
  +	
  +    </subsection>
   
   
      <subsection name="How can Collections of primitive typed elements be mapped?" anchor="19">