rpc - SOA Publishing Messages vs Calling Procedures -
the project working on moving n-tier soa architecture have been reading on soa practices. i'm struggling understand dynamic between avoiding rpc style services in favor of event driven services, , requirement of user interfaces retrieve data , speedily. so instance, ideally soa architecture composed of repeatable business process wherein publish message onto esb handle finding services handle message. rather executing procedure called "setup new user" set out tasks related new user setup, publish message esb contained new user's details , had appropriate document type "new user" , esb find services handled event whatever domain specific new user provisioning required. however, need data. maybe have page shows list of user associated data. can't fire off message esb because need data , need now. also, aren't triggering business processes; you're retrieving data invoked business processes (the processes caused user associated data instance)...