|
|
| Re: [CDO] Objectivity as CDO database [message #421976 is a reply to message #421975] |
Tue, 19 August 2008 20:09   |
 Mark Geib
Messages: 432
Registered: July 2009 |
Senior Member |
|
|
Simon,
Thanks for the reply.
So I think you are saying Objectivity is great, but not transparent, and
maybe using Objectivity via EMF/CDO reduces these issues somewhat.?
I am anxious to here your updates on this topic.
Mark.
Simon McDuff wrote:
> Good news for you Mark.
>
> Since I've been using Objectivity for the last 5 years... I can tell you
> that Objectivity is a really great tools.
> Another good news for you is I have an implementation of EMF/CDO/OO that I
> would like to give to the community very.. very soon. I've been working
> with them to finalize a few details.
>
> You have pros and cons of using Objectivity directly and CDO with
> Objectivity.
>
> Objectivity without EMF / CDO
> PROS:
> - VERY VERY fast
> - Use tools/objects developped by them directly.
> - Easy to use.
> CONS:
> - Do not have any generation of JAVA Code.
> - Locking problems
> - DeadLock
> - You could end-up having problem
> - It is easy to use... but at the same time you really need to
> understand how Objectivity is working if you don't want to shot yourself in
> the foot.
>
> Ibrahim please correct me if I'm wrong
>
>
> EMF / CDO / OO
> Pros:
> - All the features that CDO have. Notifications.. etc..
> - Easy clustering
> - No Locking problem
> - No Deadlock
> - You can change your back-end with another mechanism if you customer don't
> want to use Objectivity Inc.
> - You could move some classes to another databases.. or connect easily
> external data through EMF.
> - Benefits EMF Features.
> - All new feature EMF /CDO can provides in the future.
> - Really you are not attached from any specific database... this is really
> good!!
>
> cons:
> - In general, it will be a bit slower. You add another layer.
> - Could be faster when you have many applications accessing your database
> because of Objectivity Architecture.
>
> I have also an implementation of EMF/OO but it still have the same CONS then
> OO.
> I compared EMF/OO with Hibernate, and I can tell you that Hibernate is
> around 3 to 52 times slower than EMF/OO.
>
> You can ask me almost any question about Objectivity... I think I could help
> you. Otherwise you can ask directly support guys they are really nice!!
>
> I also played a lot with Objectivity C++.. so if you have question there as
> well!!
>
> Let me know if you want more details.
>
> Simon
>
>
>
>
>
>
> "Mark Geib" <mark.geib@echostar.com> a écrit dans le message de news:
> g8evv9$tc5$1@build.eclipse.org...
>> As a company we are looking at evaluating Objectivity for some new
>> projects with potentially HUGE databases.
>>
>> Currently we are using mysql for the CDO database, but I was thinking that
>> it may be fairly straight forward to use a true OO database in place of
>> the relational db, to still have the CDO notifications, etc.
>>
>> Does this make any sense, or would it be smarter to simply use Objectivity
>> without CDO at all. That is, persist the EMF model to Objectivity db
>> directly and do the client notifications another way.
>>
>> Any input will be appreciated.
>>
>> Mark.
>
>
|
|
|
|
|
|
| Re: [CDO] Objectivity as CDO database [message #422024 is a reply to message #422022] |
Wed, 20 August 2008 13:03 |
Cedric Brun
Messages: 431
Registered: July 2009 |
Senior Member |
|
|
Simon McDuff wrote:
> Hi Cedric,
>
> What I will provide is CDO Adapter for objectivity, not the actual
> source-code of Objectivity... I don't have that :-)
Of course :)
> To use it you will be able to download a trial of Objectivity for 60 days.
> After that it is up to you to decide if you want to pay to use it.
>
> I asked some feature for Objectivity 9.4.1 to complete my work. Once this
> is released, I will be in position to release the code.
> I hope (because I can only hope) it will be released in 1 month.
I can only hope too, the more CDO has backend, the more the technology gets validated :)
Cédric
> Simon
>
>
> "C�dric Brun" <cedric.brun@obeo.fr> a �crit dans le message de news:
> g8gj7p$7ar$1@build.eclipse.org...
>> Hi Simon,
>>
>> You're considering open-sourcing this backend right ? That would be great
>> news ! Do you know when can we expect this contribution to appear in the
>> modeling CVS ?
>>
>> C�dric
>>
>> Simon McDuff wrote:
>>
>>> Good news for you Mark.
>>>
>>> Since I've been using Objectivity for the last 5 years... I can tell you
>>> that Objectivity is a really great tools.
>>> Another good news for you is I have an implementation of EMF/CDO/OO that
>>> I
>>> would like to give to the community very.. very soon. I've been working
>>> with them to finalize a few details.
>>>
>>> You have pros and cons of using Objectivity directly and CDO with
>>> Objectivity.
>>>
>>> Objectivity without EMF / CDO
>>> PROS:
>>> - VERY VERY fast
>>> - Use tools/objects developped by them directly.
>>> - Easy to use.
>>> CONS:
>>> - Do not have any generation of JAVA Code.
>>> - Locking problems
>>> - DeadLock
>>> - You could end-up having problem
>>> - It is easy to use... but at the same time you really need to
>>> understand how Objectivity is working if you don't want to shot yourself
>>> in the foot.
>>>
>>> Ibrahim please correct me if I'm wrong
>>>
>>>
>>> EMF / CDO / OO
>>> Pros:
>>> - All the features that CDO have. Notifications.. etc..
>>> - Easy clustering
>>> - No Locking problem
>>> - No Deadlock
>>> - You can change your back-end with another mechanism if you customer
>>> don't want to use Objectivity Inc.
>>> - You could move some classes to another databases.. or connect easily
>>> external data through EMF.
>>> - Benefits EMF Features.
>>> - All new feature EMF /CDO can provides in the future.
>>> - Really you are not attached from any specific database... this is
>>> really
>>> good!!
>>>
>>> cons:
>>> - In general, it will be a bit slower. You add another layer.
>>> - Could be faster when you have many applications accessing your
>>> database because of Objectivity Architecture.
>>>
>>> I have also an implementation of EMF/OO but it still have the same CONS
>>> then OO.
>>> I compared EMF/OO with Hibernate, and I can tell you that Hibernate is
>>> around 3 to 52 times slower than EMF/OO.
>>>
>>> You can ask me almost any question about Objectivity... I think I could
>>> help you. Otherwise you can ask directly support guys they are really
>>> nice!!
>>>
>>> I also played a lot with Objectivity C++.. so if you have question there
>>> as well!!
>>>
>>> Let me know if you want more details.
>>>
>>> Simon
>>>
>>>
>>>
>>>
>>>
>>>
>>> "Mark Geib" <mark.geib@echostar.com> a ?crit dans le message de news:
>>> g8evv9$tc5$1@build.eclipse.org...
>>>> As a company we are looking at evaluating Objectivity for some new
>>>> projects with potentially HUGE databases.
>>>>
>>>> Currently we are using mysql for the CDO database, but I was thinking
>>>> that it may be fairly straight forward to use a true OO database in
>>>> place
>>>> of the relational db, to still have the CDO notifications, etc.
>>>>
>>>> Does this make any sense, or would it be smarter to simply use
>>>> Objectivity without CDO at all. That is, persist the EMF model to
>>>> Objectivity db directly and do the client notifications another way.
>>>>
>>>> Any input will be appreciated.
>>>>
>>>> Mark.
>>
http://cedric.brun.io news and articles on eclipse and eclipse modeling.
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02707 seconds
Search
Help
Register
Login
Home
