My company has chosen JCR as the standard for data management. We make integrated digital pathology solutions. Our solutions, while packaged as easy to integrate enterprise products, are built around pathology images, their acquisition and analysis and providing an efficient platform for pathologists to collaborate. An appropriate abstract definition of a Bioimagene product will be, a solution that facilitates analysis and management of pathology images. So choosing a content management system over a traditional database to store data and a file system to store images was a natural choice.

In addition to the above mentioned pitch, JCR and Jackrabbit were tremendously relevant to the types of products we are building. We are proud to be ‘right technology’ shop and we do work on the leading edge of all technology. Squeezing out every last bit of processing power and network bandwidth available to provide a smooth user experience is the driving force of our next generation innovations. Jackrabbit implementation of JCR is tremendously light in foot print and amazingly fast for content access. While we started to build an OCM layer of our own we later chose to use and at the same time improve the Jackrabbit-OCM by actively contributing to the jackrabbit open source community. The following features of Jackrabbit made our choice easier.

  1. Pluggable security model that can maintain ACL at object level
  2. Versionability for objects
  3. ability to choose the right storage device for binary content Vs. ascii data.
  4. Efficient pluggable search integration.
  5. ability to integrate with JEE environments and lightweight spring like frameworks.
  6. Import export support to and from XML.
  7. Efficient transaction management and the ability to seamlessly take part in JTA.

While Jackrabbit is feature rich using it on an enterprise application the right way is not straight forward. I do not claim our way to be the right one; It just is right for our needs. Through my posts I will be outlining the philosophy and direction of Bioimagene’s adoption of JCR. You are free to critique and suggest improvements.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Post Navigation