|
We at thinktecture are proud to unveil some of the internal conversations as we have a strong belief that they are going to help you when designing and implementing your systems. So here is the second attempt. The first one was published a couple of months ago but it was in German language ;-).
Whilst proudly announcing this I would like to express my view of one of the interesting points discussed here.
As a believer of SOA, I really like to decouple service implementation from the internal implementation(s) (Remember, I totally agree with the decision tree and I'm only talking about the extreme case here ;-)). Thus I would like to consider the service layer as a message transforming layer. For example it validates inbound/outbound messages and essentially but not necessarily converts them into its internal representation. However, just like Ralf mentions, it would be a tedious (!) task to do this mapping manually. Furthermore most of the scenarios I have seen in our life have an external representation which is quite different to its internal representation (i.e. In a canonical product line system the 'Cost' of a 'Product' means so much to the internal systems where as the external systems only concerned about the 'RetailPrice'). So we should really (as in really, really, really) have the necessary tooling to automatically do this mapping for us. At least this could be done after visually drawing the diagrams. So I strongly believe that this could be a part of the DSL tool kit ?????????.
In the future I would like to sit in front my notebook and concentrate more about my design, architecture and actual logic rather than wasting my time to key-in the same code everyday. At the end of the day I’m a lover of code generators.
|