Downloaded 39 times
Uploaded byPeter Ledbrook
Grails and the World of Tomorrow
The document discusses the evolution of web application architecture, emphasizing how Grails can adapt to modern requirements such as NoSQL, social integrations, and cloud deployment. It highlights the transformation from traditional CRUD models to more advanced architectures using CQRS and event-driven designs. The summary concludes that while Grails remains relevant with its existing features, its plugin system and event bus provide opportunities for innovative application frameworks.
More Related Content
Similar to Grails and the World of Tomorrow
Grails and the World of Tomorrow
- 1. Grails and theWorld of Tomorrow Peter Ledbrook VMware t: @pledbrook g: +PeterLedbrook e: [email protected]
- 2. NoSQL HTML5.js Concurrency Social Cloud 2
- 3. HTML5.js Web sites Applications Server-side HTML Client-side HTML Low interactivity High interactivity No offline Offline Wikipedia Twitter 3
- 4. HTML5.js We’re going this way! Web sites Applications Server-side HTML Client-side HTML Low interactivity High interactivity No offline Offline REST + JSON Backbone.js + Moustache Is this the end for GSP? 4
- 5. NoSQL Data the wayyou want it! 5
- 6. NoSQL “Everyone has interesting data” Some guy 6
- 7. Social 7
- 8. Cloud Ephemeral Easy instance filesystems creation Service-oriented architecture 8
- 9. Concurrency Responsiveness Lots of concurrent users What about all those cores? Node.js/Vert.x & the Reactor pattern 9
- 10.
- 11. Where do wego from here? • Has CRUD still got legs? • Does even MVC still make sense? • Or do we need to fundamentally change the way we write apps? What can Grails do for me? 11
- 12. A typical Grailsapp HTTP Controller View Service GORM/Hibernate Database 12
- 13. A typical Grailsapp HTTP Sticky sessions OSIVI Controller View Domain class binding Domain Service objects GORM/Hibernate Relational/object Database impedance mismatch 13
- 14. Fit for purpose? •CRUD has its place – Admin UIs – Quick UIs for complex domain models • CRUD = dynamic scaffolding • But beyond CRUD... • ... what about MVC + ORM? – Rich UIs + REST don’t need views – Do UI forms match domain classes? – Do views require the same information as updates? – How do we track changes to data? – Where should validation occur? 14
- 15. A typical Grailsapp HTTP Disable OSIVI? Controller View Command objects? Don’t let HTTP session and Hibernate session mix? Bind COs to Service @Cacheable, not domains? 2nd-level cache? importFrom(Domain) GORM/Hibernate Filtering and transforming data Database 15
- 16. Introducing CQRS Updates Store changes Concurrency via event bus Views Separate data stores for queries 16
- 17. Is it toocomplex? • PaaS makes it easy to use multiple data stores • Event bus allows for decoupling – Easier to understand than Hibernate events – Search “mirroring” would work! – Easily extended to external message broker – Synchronise multiple instances of same app on PaaS • Querying and updating already separated – PluginService & PluginUpdateService in grails.org • Groovy good for data transformations Conventions and framework support to make it easier! 17
- 18. How can Grailshelp - Rich UIs? URL mappings for REST JSON & XML converters Resources (for JS & CSS) Plugins for different UI libraries 18
- 19. How can Grailshelp - NoSQL? GORM plugins JSON handling Schemaless + dynamic lang = good! 19
- 20. How can Grailshelp - Social? Spring Social plugin, etc. Authentication via plugins 20
- 21. How can Grailshelp - Cloud? Simplified deployment with plugins Plugins for PaaS services Runtime config 21
- 22. How can Grailshelp? 22
- 23. How can Grailshelp? Plugins 23
- 24. How can Grailshelp? Plugins 24
- 25. How can Grailshelp? Plugins 25
- 26. How can Grailshelp? Plugins 26
- 27. Plugin platform Events Security UI Injection Conventions Config 27
- 28. Plugin platform Events Security 28
- 29. Plugin platform Events Security • Event bus • API + SPI • Can integrate with AMQP • Service • GORM events • Tags • App lifecycle events • Custom app events https://github.com/Grailsrocks/grails-platform-core 29
- 30. Event bus Update Call REST Save entity Index read DBs service Spring Integration Event Bus AMQP Plugins Plugins Plugins Application 30
- 31. Summary • The wayapplications are architected will change – Websites will still be built (GSP not gone yet) – Not everyone will need the same architecture – Project archetypes and scaffolding! • Grails already has many of the features we need • Plugins can add those • Plugin platform provides more powerful integration – Event bus will enable more interesting architectures 31
- 32. More info • w: http://grails.org/ • f: http://grails.org/Mailing+Lists • e: [email protected] • t: pledbrook • b: http://blog.springsource.com/author/peter-ledbrook/ 32
- 33.