Ebean has an taken a different architectural when compared with JPA and JDO and this has important implications.
Specifically Ebean does not use a 'Persistence Context' or 'Session' when it persists objects back to the database.
This means you don't need to attach/detach your beans or manage a JPA EntityManager or JDO PersistenceManager.
Persisting a bean means you just call save(). Cascade persistence is supported by traversing the relationships
on the bean.
Videos to show you various features of Ebean and options for testing.
Partial Objects and N + 1
A high performance ORM needs good support for partial objects
(only fetching the properties needed) and optimising object graph construction to mitigate
N + 1.
Ebean's query design provides a clean separation between what properties and paths to fetch and the
rest of the query (predicates, orderBy, paging) and this makes it easy for developers to optimise
object graph construction and also allows Ebean to automatically tune queries