CMS (Content Repository) and database

From Giews

The core of GiewsWorkstation looks very much like a Content management System. Therefore the question is raised wether the core can be build upon an existing CMS. This CMS could be an implementation of JSR-170 as proposed by the JCP. There are quite a number of mature implementations available at the moment. However the first question to answer is to consider the content part of Giews Workstation as a formal CMS or not!

Criteria - Will it have a negative effect on the performance? - On a low level there can be a negative effect on the performance. Is caching completely neutralizing this effect? - What is the learning curve?

Options

1. CMS Content of GWS is formalized according standards. Gives huge flexibility in adding new content types. Will make GWS more open to other systems that would like to use GWS content. 2. Database Gives more control over the database and therefore performance.

Decision Fenix will only use a database

Argumentation Using a content repository will give more flexibility in adding new datatypes. However there is a learning curve and therefore investment. Also in the current domain model there can be added a dynamic datatype with for instance for generic attribute. The static datatypes like pricing, nutrition etc. will be reflected in the domain model and in the database. Also for performance reasons, a content repository will not help.