tag:blogger.com,1999:blog-6106782.post1262603386407398698..comments2024-03-27T10:47:33.255+00:00Comments on Architecture, Data and Intelligence: What's Wrong with Layered Service Models?Richard Veryardhttp://www.blogger.com/profile/04499123397533975655noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6106782.post-36522966359751263022009-08-19T12:13:56.192+01:002009-08-19T12:13:56.192+01:00could you elaborate more on classification vs Laye...could you elaborate more on classification vs Layering with few example to understand the differences.<br /><br />We are using Thomas Erl service model. I was wondering what would be a typical anti service patternRamesh Kunhiramannoreply@blogger.comtag:blogger.com,1999:blog-6106782.post-34592393083731155052009-06-01T10:05:06.325+01:002009-06-01T10:05:06.325+01:00One of our key reasons for layering has been the s...One of our key reasons for layering has been the separation of concerns. For example, the separation of process-centric from information/data-centric capabilities. Whilst reuse is not the only driver for SOA, reuse (we prefer to say 'sharing') is hard to achieve when concerns are mixed. That is, it is hard to share data-centric capabilities in new processes, when they are bound up in another process.Lawrence Wilkeshttps://www.blogger.com/profile/03701551060177590191noreply@blogger.comtag:blogger.com,1999:blog-6106782.post-574733494403295702009-05-27T19:16:20.406+01:002009-05-27T19:16:20.406+01:00Great point on the confusion between classificatio...Great point on the confusion between classification and layering. Classification is needed to choose appropriate implementation platforms (e.g orchestration engine vs. Java app server), but that doesn't imply any particular direction of communication between the service types.Todd Biskehttps://www.blogger.com/profile/03066865865923371644noreply@blogger.com