addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

London Groovy & Grails User Group Meetup

  • Mar 18, 2013 · 6:30 PM
  • This location is shown only to members

Register with Skills Matter to ensure they know you're coming and let you in!

We have long-time Grails user David Dawson giving us an alternative application architecture to stateless services, one based on command objects! Title and abstract follow.

 

All hail the command object: are stateless services the only way?

Grails has inherited the stateless service, from spring, as one of the central ways to write a web application. It even goes as far as to make it one of the main conventions.  This works, for the most part, but is it the only way?


David discusses, with production examples, another way of using all the niceties of the grails architecture to tease out the service spaghetti and bring state and logic back together.

Join or login to comment.

  • Andrew D.

    Annoyed I missed this, stuck at work. Looking forward to the video.

    March 19, 2013

10 went

Our Sponsors

  • Skills Matter

    Hosting of the group Meetings

  • Pivotal

    Meeting Location, Food

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy