Gold sponsors

Intel logo

IBM Corporation

Cisco

JBoss

Sonatype

SAP

Oracle

Silver sponsors

Blackberry

agitar

bsi logo

Microsoft

Google

Instantiations

Soyatec

Xored

amazon

Actuate

Bronze sponsors

Purple Scout

froglogic

Paremus

objectivity

Sopera

Genuitec

itemis

excelsior

Activity sponsor

eclipsesource

Media sponsors

Methods & Tools

SD Times logo

TSSJS

Be a Sponsor

Scale, Share and Store your Models with CDO

Eike Stepper

Making With Eclipse · Extended (50 mins)
Wednesday, 14:30, 50 minutes | Stevens Creek

Tags: Modeling , Runtime
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

Are you already modeling and generating your applications with the Eclipse Modeling Framework (EMF)? Great! So you are already enjoying automatically generated model-based runtimes, structured or graphical user interfaces, XML serialization and so much more…

But what if

 

  • Your models keep growing and do not fit into memory anymore?
  • Your resources are too huge to properly fit into files?
  • You require more enterprise-like model persistence than XML serialization?
  • Your application has to be available for multiple users at the same time?
  • You need object grained locking and transactions that span multiple resources?
  • Your users appreciate to always look at the latest state of the central model?
  • They could simply switch back their view of the model to historical states?

The Connected Data Objects (CDO) model repository and distributed shared model for EMF delivers solutions to these challenges and more. CDO is a component of the EMF project for many years now and has been successfully adopted by many companies and organizations.

CDO allows you to develop your application against standard EMF APIs and decide later if you want to persist your models in any SQL database, possibly through Hibernate, in an object oriented database, in memory or what ever you can imagine. Without any changes to your application your models become really scalable on both client side and server side. Store and use models larger than four giga bytes and load up to thirty thousand objects per second to your clients. Embed your repository into your client if you don’t need distribution or embed it into a J2E container of your choice if you need other kinds of distribution. Let your users experience the collaboration on a real distributed shared model.

 

This Talk Will Show You

  • Why EMF is not enough
  • What CDO can do for you
  • How to use the APIs of CDO in order to
    • Prepare your models
    • Configure your repository server
    • Open repository sessions
    • Work with transactions and save points
    • Execute remote queries
    • Achieve pessimistic locking
    • React to remote changes
  • A demo

Eike is an independent consultant in the areas of OSGi and modeling with over 25 years of experience in software development. With his consulting company ES-Computersysteme, founded back in 1991, he conducted dozens of successful customer projects. Eike has initiated and is still actively leading the CDO Model Repository and Net4j Signalling Platform projects at Eclipse.

Visit Eike's blog for more information...