Downloaded 20 times
Uploaded byAndrus Adamchik
Apache Cayenne: a Java ORM Alternative
Apache Cayenne is a user-friendly Java ORM with a focus on community involvement and usability, currently at version 4.0. It offers a unique object persistence philosophy and features like implicit transactions, an isolated unit of work known as ObjectContext, and support for lazy object graph expansion. The framework is mature and widely used across various sectors including commercial, government, and educational organizations.
More Related Content
Similar to Apache Cayenne: a Java ORM Alternative
Apache Cayenne: a Java ORM Alternative
- 1. Apache Cayenne a JavaORM Alternative by Andrus Adamchik @andrus_a
- 2. About Me • Memberand VP of the Apache Software Foundation. • Run a company called ObjectStyle. • Open source developer: ORM, dependency injection, REST, no- container, etc.
- 3. What is ApacheCayenne • A mature user-friendly Java ORM with modeling tools. • An alternative object persistence philosophy. • Current dev version is 4.0 (209 new features and bug fixes). • Used by commercial, government and educational orgs on all continents.
- 4. History • 2001: Inception. •2002: First Alpha Release and a large production deployment. • 2006: "ObjectStyle Cayenne" becomes "Apache Cayenne". • 2016: Active project with great community.
- 5. "Community over Code" •A community-driven project under Apache Foundation umbrella. • Dozens of contributors over the years. • 8 PMC (Project Management Committee) members. • Meritocracy - anyone can earn a vote by contributing.
- 6.
- 7. Project Setup • CayenneModelerhelps to setup and maintain the project. • DB-first approach to ORM gets you started quickly with existing DB. • Auto sync of DB changes without overriding custom mapping.
- 8.
- 9.
- 10.
- 11. Editing and SavingObjects
- 12. Cayenne vs. JPA/ Hibernate
- 13. Transactions • JPA/Hibernate wereborn in the EJB world. Both are transaction- centric. • Cayenne transactions are implicit, unless you want it otherwise. • Cayenne is not connected to DB between JDBC operations. • Better connection pool reuse and no user TX code.
- 14. ObjectContext • An isolatedunit of work (each context has its own copy of objects). • Not holding any open resources (connections, etc.), doesn't need to be closed. • Fairly cheap - you can create as many instances as you need. • Can be nested (similar to nested transactions, only in memory). • Object graph can be expanded lazily as object relationships are traversed.
- 15. Persistent Object • Framework-providedsuperclass - CayenneDataObject. • No pollution with ORM annotations. • Generic property access API. • Generic mapping - can be created in runtime.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24. Why Cayenne? • Mature,performant, user-friendly. • Opinionated on the side of usability. • Not obsessed about transactions. Smooth object graph navigation. • Community-driven. You can have a voice!
- 25. Questions? • @ApacheCayenne • http://cayenne.apache.org/ •https://github.com/apache/cayenne