Hi,
Thank you for your answer.
Yes, you are correct… I’m comparing apples with oranges… But they do the same thing: store data.
What I’m doing here is just trying to find the best model for the database to use in my project. My data can be easily converted to the relational model, XML , OO…
I can use a relational, native XML, object oriented or other type of database. I can use Tamino, Oracle, SQL Server, Objectivity or other… but must justify why.
So, I think I can compare apples and oranges, because they are all fruits… I think this is not easy to do because as you said they all work differently. But I must justify my choice in some way. What I should do is find a fair way to this.
My idea is the end user doesn’t need to know what database is supporting the application he/she is using.
Regarding my experiment, I used indexes (standard and text) on the attributes I queried.
Perhaps in the future a new Starter kit will be available with a more recent version of Tamino, so I can try it.
Thank you again for your answer.
JN
#webMethods#webMethods-Tamino-XML-Server-APIs#API-Management