Using "Grails" and utilizing SpringSource, we shall offer a hands-on demo introducing a typical "Grails" development environment and a classical cloud computing application deployed and managed on top of Amazon CC services.

1. By : Zvika Markfeld Tikal Knowledge < RSS In The Clouds Grails App on AWS Cloud

3. Stuff about Grails

4. Demo

5. Conclusions, Directions

6. Q & A

7. But First, Stuff About Me Zvika Markfeld Working in Java Server / Web / Client arena over the past decade Consulting with Tikal over the past 7 years Web (Struts, JSF, WebWork, GWT, JS) Serverside (JXXX, Spring, Hibernate, XML) New to Cloud, familiar with open technologies Going on an adventure together...

8. The AWS Cloud

9. AWS Cloud – Instance Virtualization

10. AWS Cloud

11. Storage, CPUs, Shell, ...

12. OS Snapshots, the works

13. Steady Address

14. “Even threw in my very own shell...”

15. Strong Foundations, Raw Interface

17. “ Pay As You Go”

18. Scalable, load-balanced

19. Instant

20. Virtual (usually a good thing)

21. But then again................ Infrastrwha?! Pretty Slick, On The Whole...

23. What I still want a non-crippled JVM?

24. CloudFoundry: Far More Civilized Way

26. “Application lifecycle management for running Spring, Grails, and Java web applications”

27. [Currently] “running on Amazon Web Services infrastructure”

28. “Scales from a single machine instance to a high availability multiple load-balanced ones”

30. “Application lifecycle management for running Spring, Grails, and Java web applications”

31. [Currently] “running on Amazon Web Services infrastructure”

32. “Scales from a single machine instance to a high availability multiple load-balanced ones”

33. Central, Applicative Management

34. Happy DBasing

35. Monitoring for Dummies (?)

36. SpringSource Support (STS, Grails)

37. PC -> Cluster -like Effect

38. Selective Fine Grain-ness

39. App Server, Database, ...

40. Platform-like

41. Business isn't always bad for Technology

42. Time To Meet Grails

43. While sifting through Web MVC frameworks...

45. View: GSP, layout with SiteMesh, dynamic tag libs

46. Controller

49. Extensive, expandable CLI

50. Jetty/Tomcat ready

52. Constrainable ...But Different

57. Pre integrated with a few other technologies...

59. Hibernate : ORM, querying mechanism...

60. Groovy : for focusing on everything that matters

61. And: SiteMesh, Quartz, AJAX frameworks...

62. Built upon solid bricks & best of breed components

65. Groovy Compiles to Java runtime code

67. Familiar (weeeell, kinda)

68. Libraries, well known usage patterns Oh, And Did I Mention...

69. Keeps Simple Things, Simple

70. GSP views, tag-driven

71. Criteria HQL DSL (Gone DAOs Smell!)

72. Relatively Well-Documented

73. Demo

74. Code? Configuration? Meet DSL

75. Cloud Foundry Plugin Configuration

76. Declarative Security (Security Plugin)

77. Some More Snips On Eclipse...

79. Easy Coding (at low LOC)

80. Easy Setup & Management

81. Resource Decoupling

82. All these should yield, on the paper, High adoption rate...

83. Open? 2/3 *(

85. Business-oriented, allows financial scalability

86. Virtual, quick to setup and destroy

87. Foundation phase over: Production-(almost)-ready

88. Deployment hell made manageable

91. / A