|
|
Re: EMFStore vs. CDO [message #1678800 is a reply to message #1668743] |
Mon, 16 March 2015 10:45 |
Jonas Helming Messages: 699 Registered: July 2009 |
Senior Member |
|
|
Hi Franco,
I think it makes sense to define your requirements more in detail. Examples:
- Number of Users?
- Expected Model Size?
- Online vs. Offline?
- How should conflicts be handled?
- and many more
based on that I would spend some time on an evaluation to make sure you
find the best technology for your use case. Depending on the kind of
application you develop, there is even a third alternative: Git in
combination with EMF Compare.
About the scalability of concurrent Users in EMFStore: As the default
Mode in EMFStore is offline, the server only gets active, once a user
(or a system) triggers a commit or update. Of course it depends on the
total number of users, you want to support, but typically the model size
is a more critical factor. If you need to support very large model
instance (millions of elements), the loading and unloading feature of
CDO can help.
Best regards
Jonas
--
Get professional Eclipse developer support:
http://eclipsesource.com/en/services/developer-support/
Am 13.03.2015 um 06:02 schrieb Franco Lombardo:
> Hi all,
>
> I'm choosing the persistence engine for a project that uses EMF, and I'd
> like to know if I should use EMFStore or CDO. Consider that in my use
> case this engine will be heavily used by many concurrent clients, so
> scalability could be an issue.
>
> I did some test with CDO and the MongoDBStore, because I thought to use
> the scalability features of this DB, but it seems to me that this
> project is not longer supported, isn't it?
>
> Thank you very much.
>
> Franco
>
--
Get professional Eclipse developer support:
http://eclipsesource.com/en/services/developer-support/
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06087 seconds