Understanding GORM (Greach 2014)
•
6 gostaram•3,684 visualizações
GORM is one of the keys for the success of Grails, but for a Grails beginner some concepts may be a bit confusing. Even for a long time developer there can be some missconceptions due to the abstractions layers of the framework. In this talk I’ll try to cover some of the basics of GORM, Hibernate and how to interact with transactions and sessions. I’ll show some of the problems that I had starting with the Grails framework and how I think they are best solved. Some other topics that I’ll go over are the interaction with GPars, and the differences between “session” and “transaction”.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (8)
Semelhante a Understanding GORM (Greach 2014)
Semelhante a Understanding GORM (Greach 2014) (20)
Último
Último (20)
Understanding GORM (Greach 2014)
- 1. UNDERSTANDING GORM Alonso Torres @alotor http://goo.gl/U6sK5E
- 2. Ego-slide Alonso Torres alotor @alotor Engineer atKaleidos
- 3. GORM? Really? Is so easy, the easiestpartof Grails! Onlyafew POGO's to access the database Peachy!
- 5. Some pitfalls The 'When did I modified thatobject?' defrenderBook(Stringisbn){ defbook=Book.findByIsbn(isbn) //Renderasuppercase book.title=book.title.toUpperCase() [book:book] }
- 6. Some pitfalls The 'Rollback where are you?' defbuyBook(Stringuser,StringbookTitle,Longqty){ deffound=Book.findByTitle(bookTitle) //Saveaneworderfortheuser deforder=newBookOrder(user:user,book:found,quantity:qty) order.save() found.stock=found.stock-1 //Whennotfoundthrowexceptiontorollback if(found.stock<0){ thrownewException("Thisshouldrollback!") } returnfound }
- 7. Some pitfalls The 'Parallelprocessing, It's easy!!' defprocessOrders(){ deforders=BookOrder.list() //Parallelupdateorders GParsPool.withPool(10){ orders.eachParallel{order-> dispatchingService.dispatch(order) order.sent=true order.save() } } }
- 9. GORM is dark and full of terrors
- 10. Let's take a step back... and start at the beginning
- 11. Understanding Bootstrapping WHAT'S GOING ON BEHIND THE SCENES?
- 12. Your first Domain class
- 14. Grails Bootstrap Inspect/grails-app Classes inside /domain Annotates them with @grails.persistence.Entity grailsrun-app
- 15. 1) Domain classes are found
- 17. Grails initializes the Domain Class Prepares the relationship properties Resolves class hierarchy Add validation capabilities Integrates domain classes with Spring
- 18. @grails.persistence.Entity Includes 'id'and 'version' Marks the classes as domain entities You can putdomain classes inside /src/main/groovy Manualyannotate them with @Entity
- 20. 2) GORM enhances classes
- 23. GORM Enhancer Instances API (save, delete...) Classes API (findAll, where, withCriteria...) Dynamic Finders Validation (unique)
- 24. GORM Enhancer Instances API (save, delete...) Classes API (findAll, where, withCriteria...) Dynamic Finders Validation (unique)
- 25. Bootstraping DistinctGrails-base vs GORM @Entitycould potentialybe used outside Grails Problems with AST's Grails dependencies
- 26. Understanding Spring HOW INTERACT DOMAIN CLASSES AND SPRING
- 28. DI needs control on object instantiation Spring should create the object newBook()
- 29. So Grails kind of "cheats"
- 30. Spring Beans for a Domain Class BookValidator BookPersistentClass BookDomainClass Book
- 32. What does that means? Springcreates your objects Be carefulwhen usingsome capabilities Example: SpringAOP
- 33. Understanding Hibernate GORM WHERE THE DARKNESS LURKS
- 34. GORM > Hibernate GORM provides abeautifulabstraction over hibernate Convention over configuration No more complicated XML or annotations Better collections
- 35. But, Hibernate it's still there
- 39. OpenSessionInViewInterceptor Creates anew Sessionwithin aController scope Doesn'tcreate aTransaction So... there is NO transaction atthe controller After render the session is flushed
- 40. Session? Transaction? I'm confused
- 41. Session Entrypointto the Hibernate Framework In-Memorycache No thread safe and normalythread-bound
- 42. GORM Entities Entities have arelationship with the session This defines a"life-cycle" Transient -notyetpersisted Persistent -has asession Detached -persisted butwithoutsession
- 44. Session Flush Session checks "DIRTY OBJECTS" When flushed the changes are persisted to database
- 45. After flush, are my objects in the DB? DEPENDS
- 46. Transaction Database managed Provider specific Accessed through JDBC Driver
- 49. Automatic session flushing Queryexecuted Acontroller completes Before transaction commit
- 50. Some pitfalls The 'When did I modified thatobject?' defrenderBook(Stringisbn){ defbook=Book.findByIsbn(isbn) //Renderasuppercase book.title=book.title.toUpperCase() [book:book] }
- 51. Some pitfalls The 'When did I modified thatobject?' defrenderBook(Stringisbn){ defbook=Book.findByIsbn(isbn) //Deattachtheobjectfromthesession book.discard() //Renderasuppercase book.title=book.title.toUpperCase() [book:book] }
- 52. Where do I put my transactional logic?
- 56. Be careful! Don'tinstanciate the services Don'tuse closures And... newTransactionalService().doTransactionalStuff() deftransactionalMethod={...}
- 57. DON'T THROW CHECKED EXCEPTIONS
- 58. Some pitfalls The 'Rollback where are you?' defbuyBook(Stringuser,StringbookTitle,Longqty){ deffound=Book.findByTitle(bookTitle) //Saveaneworderfortheuser deforder=newBookOrder(user:user,book:found,quantity:qty) order.save() found.stock=found.stock-1 //Whennotfoundthrowexceptiontorollback if(found.stock<0){ thrownewException("Thisshouldrollback!") } returnfound }
- 59. Some pitfalls The 'Rollback where are you?' defbuyBook(Stringuser,StringbookTitle,Longqty){ deffound=Book.findByTitle(bookTitle) //Saveaneworderfortheuser deforder=newBookOrder(user:user,book:found,quantity:qty) order.save() found.stock=found.stock-1 //Whennotfoundthrowexceptiontorollback if(found.stock<0){ thrownewRuntimeException("Thisshouldrollback!") } returnfound }
- 60. @Transactional vs @Transactional Spring@Transactionalcreates aPROXY Grails new @Transactionalis an AST
- 61. Understanding Parallel GORM BRACE YOURSELVES
- 63. Some pitfalls The 'Concurrency, It's easy!!' defprocessOrders(){ deforders=BookOrder.list() //Parallelupdateorders GParsPool.withPool(10){ orders.eachParallel{order-> dispatchingService.dispatch(order) order.sent=true order.save() } } }
- 64. Thread-local session Recovers alistof orders Each item is bound to the requestsession When we spawn the concurrentthreads the objects don't know where is their session deforders=Orders.findTodayOrders()
- 65. Some pitfalls The 'Concurrency, It's easy!!' defprocessOrders(){ deforders=BookOrder.list() //Parallelupdateorders GParsPool.withPool(10){ orders.eachParallel{order-> BookOrder.withNewSession{ order.merge() dispatchingService.dispatch(order) order.sent=true order.save() } } } }
- 66. Rule of thumb Session = Thread If entityhas recovered byanother thread Putitin the currentthread session
- 67. Grails 2.3 Async GORM The new async GORM solves some problems Manages the session for the promise defpromise=Person.async.findByFirstName("Homer") defperson=promise.get()
- 68. Grails 2.3 Async GORM Problem: Objecthas been retrieved byanother thread After the promise is resolved we have to attach the object defpromise=Person.async.findByFirstName("Homer") defperson=promise.get() person.merge()//Reboundtheobjecttothesession person.firstName="Bart"
- 70. Closing thoughts GORM is averycoolabstraction You have to be aware of some of how things work With greatpower, comes greatresponsibility