On 22 Jan 2013, at 18:35, Graham Ashton <[email protected]> wrote: > 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
I read that this afternoon, planning to go through it again with my own examples tomorrow. > 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. How synchronous did this message passing need to be? That sounds like for our application a deep dive into latency hell if not managed carefully. I'm already fighting that on one part of the setup with some controller actions on the website needing tens of seconds to do their thing. > 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? It might be difficult to do that on a public list and to maintain commercial confidences. Are you likely to be at an LRUG or NWRUG any time soon? Failing that, I might be able to be a bit more explicit off-list. Thanks, Paul -- 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.
