Dedicated set of either WCF SOAP or REST services to do reads / queries for data, the results of which you databind to your views using strongly typed views + MvcContrib FluentHTML or some other similar toolkit. I suggest WCF only because you're already using that, but you could be retrieving data from a static XML file on disk or a distributed cache that is kept up to date using pub/sub with RSB. Doing request / response messaging with RSB or any of the other messaging frameworks is painful - and it's painful for a reason - you shouldn't do it. On the other side of the equation you have the writes that your application performs - it's easiest IMO to send those through the message bus and carry out the commands in message consumers which then publish events that your read/query sources consume.
HTH, Matt On Tue, Jun 16, 2009 at 12:25 PM, Craig Neuwirt<[email protected]> wrote: > I have an ASP.NET MVC application full of ActiveRecord databinding and > Finders (Specifications) for data access. WCF is used to communication > with services. I will no longer have access to the database in the MVC > Application layer so my plan is too replace all WCF with Rhino ESB. > However, I am not sure what the best approach to replace the AR DataBinding > and other data access. Should you use messages for that too or stay with a > more traditional service to handle data access. I definitely don't want a > bunch of distributed repositories with an ever increasing number of methods > to retrieve different pieces of data. > Any ideas or suggestions would be appreciated. > thanks, > craig > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
