InfoQ Homepage Presentations Reactive Oriented Architecture with Grails
Reactive Oriented Architecture with Grails
Summary
Steve Pember discusses the tenants of the Reactive Pattern and the importance of moving away from Monolithic to Reactive architectures. He also discusses the various Groovy-friendly technologies that allow us to build distributed, micro-service based applications and cover effective communication strategies between each service.
Bio
Steve Pember is Software Developer, CTO of ThirdChannel.
About the conference
Pivotal and No Fluff Just Stuff bring you SpringOne 2GX 2014, a one-of-a-kind conference for application developers, solution architects, web operations and IT teams who develop business applications, create multi-device aware web applications, design cloud architectures, and manage high performance infrastructure. The sessions are specifically tailored for developers using the hugely popular open source Spring IO projects, Groovy & Grails, Cloud Foundry, Hadoop and Tomcat technologies. Whether you're building and running mission-critical business applications, designing the next killer cloud or big data application, SpringOne 2GX will keep you up to date with the latest enterprise open source technology.
Community comments
Slides
by Ron Dagostino,
Re: Slides
by Roxana Bacila,
Re: Slides
by Roxana Bacila,
Distributed Query services
by Cédric Escher,
Slides
by Ron Dagostino,
Your message is awaiting moderation. Thank you for participating in the discussion.
Slides are not updating with the presentation
Re: Slides
by Roxana Bacila,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi Ron,
Thank you for pointing it out. We are currently working on fixing it.
Re: Slides
by Roxana Bacila,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi Ron,
This is now fixed and presentation should be working fine. Please let us know if you encounter any other bugs.
Distributed Query services
by Cédric Escher,
Your message is awaiting moderation. Thank you for participating in the discussion.
I understand how I can benefit from events and msg brokers to alter data, but how can I efficiently create services to collect data.
Let's say a user goes to his account to see his order history, I'd need a service like "getOrders()" which would be part of the "Order Microservice". Now, this service must be exposed with REST (or any other protocol) how can I avoid writing a REST client for every client (lets say the user frontend would be one). Is there an automatic way how to proxy this service and use this library in a plugin (like in good old EJB). What is the best practice there?