[TYPO3-mvc] SOAP call using extbase

[Jochen Rau]

Hi Masi.

On 12.04.10 09:22, Martin Kutschker wrote:
> No. He somewhere * wraps up the two goals the model must meet:
>
> a) it must be consistent with reliaty
> b) must be implementable (with reasonable performance)
>
> As far as I understand he wants to be true to his design goals without loosing touch with real code.
> Creating an application in the DDD methodology (again my reading) is very different from an academic
> ivory tower design. If the code doesn't fly, the model is broken. That's why I'm a bit wary when I
> hear that "concept X" solves all your needs and you never have to worry again about a DB or
> underlying systems. That's only true to a certain degree. If you design your model against the
> underlying layers your application won't work properly.

I fully agree, that DDD is a methodology that is focused on solving real 
world problems. That's one of its core goals. And I agree that the 
underlying technical solution must perform well and must be reliable (in 
sense of data corruption or loss).

But I did not say at any time that a developer never has to "worry again 
about a DB or the underlying systems". On the contrary, it is crucial 
for a developer to understand the underlying systems (DB, file system, 
SOAP, whatever), to know about their pros and cons. Then, having this in 
depth knowledge, you should use the Repository pattern to abstract from 
the underlying system.

And what does this abstraction mean? It is not an "ivory tower" 
abstraction. IMO there are many advantages of this abstraction:

1) You can change the storage solution or the implementation of the 
Repository without touching the consumers code.
3) You can use domain language to query for Objects.

IMO the first one is overrated. I never changed form one database vendor 
to another, did you?

The second one is the most important one. If I have already implemented 
a SoapRepository, I can solely focus on the domain.

Regards
Jochen

BTW Nice discussion! ;-)