Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Iván López Martín, profile picture
Uploaded byIván López Martín
1,710 views

GGX 2014 - Grails and the real time world

Iván López discusses the advantages of event-driven architectures over traditional request-response architectures, highlighting improved performance and reduced customer wait times. He presents implementation examples using Grails, emphasizing loose coupling, scalability, and high performance. The session concludes with a summary of Grails' standard architecture and considerations for application development.

Technology◦
Downloaded 12 times
Iván López @ilopmar GRAILS AND THE REAL-TIME WORLD
Hello! I am Iván López @ilopmar @madridgug http://greachconf.com
Traditional architectures Request-response POST /register-user POST /register-user POST /register-user
Traditional architectures
Traditional architectures
“ A problem postponed is a problem solved. Really?
1. Event Driven Architectures
Event Driven Architecture ▷ Fire & Forget ▷ Decouple producer and consumer ▷ Immediate action in the consumer ▷ Real-time
Traditional architecture POST /purchase POST /purchase - Receive request 5 ms - Data validation 20 ms - Save 40 ms - PDF generation 200 ms - Send email 80 ms - Render response 50 ms Total: 395 ms
“ Can we do it better?
Event driven architecture POST /purchase POST /purchase - Receive request 5 ms No - Data validation 20 ms No - Save 40 ms No - PDF generation 200 ms Yes - Send email 80 ms Yes - Render response 50 ms No Total: 115 ms ~ 70% better Can anyone else do it?
Event driven architecture POST /purchase PDF Generation POST /purchase - Receive request 5 ms - Data validation 20 ms - Save 40 ms - Render response 50 ms Total: 115 ms Send email
“ Don't keep your clients waiting unnecessarily! Can I defer it?
Goals ▷ Loosely coupled architecture, easy to extend and evolve ▷ Build high performance and scalable systems ▷ Keep the business logic where “it belongs”
What about Grails? ▷ Platform core ▷ Events plugin ▷ Executor plugin ▷ Grails 2.3 async
Synchronous example // Send confirmation email def user = new User(params).save() emailService.sendRegistationMail(user) render view:'registerOk' class EmailService { public void sendRegistrationMail(User user) { sendMail { to user.email subject "Confirm your account" html g.render(template: "userEmailConfirmation") } } }
Asynchronous example // Platform core def user = new User(params).save() event('sendRegistrationMail', user) render view:'registerOk' class EmailService { @grails.events.Listener public void sendRegistrationMail(User user) { sendMail { to user.email subject "Confirm your account" html g.render(template: "userEmailConfirmation") } } }
Asynchronous example // Executor def user = new User(params).save() runAsync { emailService.sendRegistationMail(user) } render view:'registerOk' class EmailService { public void sendRegistrationMail(User user) { sendMail { to user.email subject "Confirm your account" html g.render(template: "userEmailConfirmation") } } }
“ I love the smell of code in the morning
What if we don't want this? ▷ Extract “dependencies” to configuration ▷ Change the application behaviour modifying the configuration
Spring Integration Use inside Spring the well-known Enterprise Integration Patterns http://www.enterpriseintegrationpatterns.com/
Spring Integration ▷ Lightweight messaging mechanism for Spring applications ▷ High level abstraction for messaging ▷ Application code is not aware of the messaging API ▷ External systems integration declaring adapters
Message ▷ Payload ▷ Header ▷ Immutable
Channel ▷ Point-to-point ▷ Publish-Subscribe
Endpoints ▷ Transformer ▷ Filter ▷ Router ▷ Splitter ▷ Aggregator ▷ Service activator ▷ Channel-adapter ▷ Enricher ▷ Bridge ▷ ...
Adapters ▷ JMS ▷ AMQP ▷ TCP ▷ UDP ▷ File ▷ FTP ▷ RMI ▷ HTTP (Rest) ▷ WS ▷ Mail ▷ JDBC ▷ XMPP ▷ Twitter ▷ RSS ▷ MongoDB ▷ Redis ▷ Gemfire ▷ Stream
“ Talk is cheap. Show me the code.
2. Demo
3. Summary
Summary ▷ Grails standard architecture fits in most of the cases ▷ It doesn't scale to infinite (and beyond!) ▷ Think about the application you're building ▷ Think about information flow
Thanks! Any questions? Iván López @ilopmar lopez.ivan@gmail.com https://github.com/lmivan http://kcy.me/1dwf7