Introduction To Grails

2,895 views
2,873 views

Published on

Presentation done at the Utah Ruby User Group meeting on Groovy / Grails. I cover some similarities and differences between Grails and Rails.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,895
On SlideShare
0
From Embeds
0
Number of Embeds
1,092
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide















  • Introduction To Grails

    1. 1. Introduction to Groovy & Grails
    2. 2. ‣ Builds upon the strengths of Java but has additional power features inspired by languages like Python, Ruby and Smalltalk ‣ Makes modern programming features available to Java developers with almost-zero learning curve ‣ Supports Domain-Specific Languages and other compact syntax so your code becomes easy to read and maintain ‣ Simplifies testing by supporting unit testing and mocking out-of-the-box ‣ Seamlessly integrates with all existing Java objects and libraries ‣ Compiles straight to Java bytecode so you can use it anywhere you can use Java
    3. 3. "Groovy is like a super version of Java. It can leverage Java's enterprise capabilities but also has cool productivity features like closures, builders and dynamic typing. If you are a developer, tester or script guru, you have to love Groovy."
    4. 4. !=
    5. 5. != ** but Rails paved the way
    6. 6. Development modes (development, test, production, custom) • Built-in web server • Hot deploy / class reloading without restarting the server • ORM (Object Relational Mapping) • Lots of plugins, that can be downloaded from the command line / plugin manager • Simple routing configuration • Model, view, controller, and test generators • Active community • Easy to learn • Full stack frameworks • Console (groovysh / groovyConsole) • Easy to configure • Builders • Very easy to create tags / reusable HTML components • Convention over Configuration
    7. 7. Services Classes which contain business logic but are not necessarily tied to a specific domain class (ie. model)
    8. 8. Services Classes which contain business logic but are not necessarily tied to a specific domain class (ie. model) No Migrations SQL generation is done through the domain class. You define how the domain class should be structured, and the SQL is generated.
    9. 9. Services Classes which contain business logic but are not necessarily tied to a specific domain class (ie. model) No Migrations SQL generation is done through the domain class. You define how the domain class should be structured, and the SQL is generated. Plugins Plugins written for Grails are simply Grails applications that override existing code. Similar to Rails Engines, but done right.
    10. 10. Services Classes which contain business logic but are not necessarily tied to a specific domain class (ie. model) No Migrations SQL generation is done through the domain class. You define how the domain class should be structured, and the SQL is generated. Plugins Plugins written for Grails are simply Grails applications that override existing code. Similar to Rails Engines, but done right. Java Integration Any Java jars or code libraries can be used within the Grails application easily.
    11. 11. Demonstration
    12. 12. 1st Thursday of every month at 6:30 PM Neumont University Room #308

    ×