Grails in 5mins (2010-v0.3)
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
206
On Slideshare
206
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. The Grails Framework in 5 minutes David Trattnig, 2010
  • 2. Full-Stack Framework• Presentation• Business Logic• Persistence• Build & Test• Documentation photo credits: http://www.flickr.com/photos/slipstreamjc/748716731
  • 3. An evolution. Java EE Java Language JDK Java Virtual Machine• Leverages existing resources (works with „JVM friendly“ hardware, software and humans)• Build upon industry-proven technologies (established, well tested and scalable Java frameworks & libraries)
  • 4. Convention over Configuration (CoC)• No more painful XML settings• 80 / 20 rule• Don‘t repeat yourself (DRY) photo credits: http://www.flickr.com/photos/squirmelia/2451382877
  • 5. Domain Driven Design (DDD)• Focus on the domain, rather than technology• Rapid prototyping• Adaptable architecture photo credits: http://www.flickr.com/photos/garibaldi/209338463
  • 6. Grails Plugin System • 350+ Plugins available • Modularized app architecture • Reuse established Java librariesphoto credits: http://www.flickr.com/photos/oskay/265899865, http://www.flickr.com/photos/oskay/265899967, http://www.flickr.com/photos/oskay/265899811/
  • 7. Groovy, the language• Less and more expressive code• Mix Java & Groovy• Dynamic language for changing requirements• Compiles to Java bytecode• „Relaxed“ learning-curve for Java programmers
  • 8. Possible Pitfalls• difficult debugging - nature of dynamic languages (but enforces proper test-cases)• multiple sources for possible defects (stack of many but well-tested Java frameworks)• „Fear of learning a new language“ (Split the project in a Grails-Part and pure Java-Part for „traditional“ developers)
  • 9. Success Stories... ... are happy with