I've got a write up of how I refactored a Rails controller with some of the hexagonal ideas here:
https://www.theagileplanner.com/blog/building-agile-planner/refactoring-with-hexagonal-rails In that post I talk about the observer pattern (not to be confused with the "observer" code in Rails). I learnt to love observers on the biggest project I've ever been involved with (Python, with no web stuff in sight), which was very SOA, with 7 different services sending messages to each other over a home grown message bus. It was big, but the responsibilities of each component were clear. Paul - I haven't chipped in on this thread until now because I wasn't sure how useful I could be without a bit more context. Would it be easy to flesh out what the system does, and what the various services involved are responsible for? Francis Fish <[email protected]> wrote: >On Tue, Jan 22, 2013 at 1:24 PM, Colin Densem <[email protected]> >wrote: > >Where I've used it the real pain has always been around testing. Versioning of >the endpoints is I'd say mandatory, coupled with the most fragile of >assumptions, human nouse. Actually deploying it, designing it I find a little >easier when separated to logical points. > >+1 for versioning, if I remember right we had to make sure the version was in >the URL 'cos nginx doesn't include params in the cache key. In fact the whole >service call, somehow? Memory fades, it's been 18 months. > >Apologies for length, off to read up on hexagonal, missed that somehow. > >http://rubyrogues.com/078-rr-hexagonal-rails-with-matt-wynne-and-kevin-rutherford/ > > >+1 > >-- >You received this message because you are subscribed to the Google Groups >"NWRUG" group. >To post to this group, send email to [email protected]. >To unsubscribe from this group, send email to >[email protected]. >For more options, visit this group at >http://groups.google.com/group/nwrug-members?hl=en. -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en.
