CDO: Satisfy Your Requirements Before You Even Know You Have Them





Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Nov 26, 2013

Suppose you must develop an application to support someone's business processes and you accepted a set of requirements and agreed upon the underlying data model. Being eager to deliver, you employ the Eclipse Modeling Framework (EMF) to generate the interfaces and implementation classes of the model. Then you implement your functional requirements by programming against the generated model interfaces and you think you're done. In this session I'll explain the ten reasons why you're not and how you could have been.

You've overlooked the following:
- Scalability
- Thread safety
- Database persistence
- Multiuser transactional access
- Collaboration
- Security
- Auditing and branching
- Data integrity
- Fault tolerance
- Offline availability

You'll leave this session with a good understanding of why you would have been done if you had chosen the Connected Data Objects (CDO) platform to satisfy these technical requirements.


When autoplay is enabled, a suggested video will automatically play next.

Up next

to add this to Watch Later

Add to

Loading playlists...