I have an EMF model that I need to persist to a database. I'd like the
model to be able to reference RTC users, workitems, and team areas, so
persisting the model in the RTC repository seems ideal. Our
application needs to use dynamic EMF to extend one or more of the
modeled classes to add user specified attributes. Conceptually, it
seems identical to how a user can customize a workitem. In fact, I
would like to allow users the ability to specify the additional
attributes as part of the process configuration data.

Can this type of model be persisted in the RTC repository? Do the
dynamically added attributes get mapped to columns in the table with
the base attributes so that they can be queried efficiently? Do I have
to write code to add the columns?

Another concern I have is performance. We will be inserting somewhere
in the range of 20 to 200 instances of the model per second. Does
anyone have a "gut feel" if RTC can handle that insert rate along with
updates, queries, etc? If the answer is "we can't handle that", how
much effort would it be to store a model (using something like Teneo)
that somehow ties back into RTC so that my UI can have links to RTC
users, workitems, etc?

Right now, I'm trying to evaluate Teneo, RTC, and developing a custom
solution. Any words of wisdom will be appreciated.

Bryan