The document discusses best practices for developing Grails applications including using domain-driven design, test-driven development, validating user input, following Grails conventions around services and controllers, using command objects, avoiding code duplication, and taking a test-driven development approach with frequent testing and code coverage. It also mentions using plugins and customizing or overriding plugins when needed.

1. Springone 2GX 2015
Tom Henricksen

4. ● Use domain-driven design
● Test Driven
● Validate

5. class User {
...
static constraints = {
login size: 5..15, blank: false, unique: true
password size: 5..15, blank: false
email email: true, blank: false
age min: 18
}
}

6. ● Follow Grails conventions
● Service as Transactional
● Functional Logics

7. ● Location
● Naming

8. ● Keep Controller thin
● Use the proper naming convention
● Use command object

9. @grails.validation.Validateable
class LoginCommand {
String username
String password
static constraints = {
username(blank: false, minSize: 6)
password(blank: false, minSize: 6)
}
}

10. ● Use for Transactional
● Avoid code duplication
● Statelessness

11. ● Override setters and getters
● De-merge complex query
● Restrict logic
● Use objects to model logic

12. ● Reusable plugins
● Public plugin repository
● Use fixture plugins
● Override plugin

13. ● TDD Approach
● Test Often
● Use test coverage
● Favor unit over integration