tag:blogger.com,1999:blog-2120400492278270391.post7735356288514249215..comments2023-08-23T06:57:04.599-07:00Comments on Enterprise Architecture - A Practitioner's View: What can SOA learn from RDBMS?Chris Birdhttp://www.blogger.com/profile/13436436994311245922noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-2120400492278270391.post-37762284321298089502008-06-15T21:47:00.000-07:002008-06-15T21:47:00.000-07:00The concepts make sense, and I think I understand ...The concepts make sense, and I think I understand the thoughts behind moving the "trigger" lifecycle management system away from the database ( which presumably is one of the stoes where the records of the businss events are either "permanently" or "temporarily" captured. Having said that, and using the example of the interesting event you referenced, I would expect that the completion of an event such as confirmation of the sales order , would be accompanied by an update in a database or many of them somewhere. It would seem that the database update would be the equivalent of the signature on the order, rather than the excited declarations of victory from the sales team, which might in my simple mind be something like the services chatter one might get, before the signature event.Anonymousnoreply@blogger.com