[TYPO3-dev] The extbase dilemma

[Daniel Brün]

Hi again,

from the replies one might get the impression that extbase causes problems
only with huge databases. That is not the case. Every single
extbase-extension out there has the race condition problems I mentioned...
you probably just have not noticed yet.

I completely agree with Dmitry. In classic TYPO3-extensions you could easily
take care of persisting data. You could even easily access tables that have
no TCA-Configuration and take care of transactions yourself (and leverage
database-features as needed).
If you want to do so in extbase, you more or less have to say goodbye to
your domain objects. There is no reasonable middle way.
Extbase wants you to completely stay away from SQL, which can not be an
option if the relational mapper is too weak to handle basic queries.

Fluid also has some problems, but these might be easier to tackle. Fluid is
just plain slow. You can use non-existing variables and Fluid might hide the
errors from you. Fluids teamplating-paradigma is all or nothing, there is no
concept for overlays. Templates have to reside in a single directory.
Basically, there are just a bunch of annoyances that can certainly be fixed.

Cheers,
Dan


2011/5/18 Daniel Brün <bruen at saltation.de>

> Hi,
>
> 2011/5/18 Dmitry Dulepov <dmitry.dulepov at gmail.com>
>
>> Hi!
>> Sebastian Kurfürst wrote:
>>
>>> You're right; and that's the same for TYPO3 v4 -- no use of transactions
>>> there as well (correct me if I'm wrong); so while I agree that
>>> transactions would be nice, we have lived in TYPO3 v4 for ages without
>>> them.
>>>
>>
>> These two approaches cannot be easily compared. With pure v4 you can start
>> transaction on your own because you control database queries: you know where
>> you do inserts, updates and deletes. With Extbase you don't known that. Even
>> more: you shouldn't use direct database access. So it is not the same.
>
>
> That is exactly the point.
>
>  For me, the most prominent purpose of Extbase is to let people learn
>>> Domain-Driven Design and the associated FLOW3 paradigms in a known
>>> environment, and to gain real-world experiences with these techniques.
>>>
>>
>> It seems that this is the problem: people do not use Extbase for the
>> intended purpose (to learn DDD). They use Extbase to create extensions. The
>> purpose does not match the use. Sounds humorous but that's what we have.
>>
>>
> Dmitry: douze points.
>
>
>>
>> --
>> Dmitry "itoldyou" Dulepov
>> TYPO3 core&security team member
>> E-mail: dmitry.dulepov at typo3.org
>> Web: http://dmitry-dulepov.com/
>>
>> _______________________________________________
>> TYPO3-dev mailing list
>> TYPO3-dev at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>>
>
>
>
> --
> *Daniel Brün*
> *fon*: +49 (0) 521 - 329647-11
> *fax*: +49 (0) 521 - 329647-40
> *e-mail*: bruen at saltation.de
> http://www.saltation.de
> ---------------
>
> saltation GmbH & Co. KG | Niederwall 43 | 33602 Bielefeld
>
> Sitz Bielefeld | Amtsgericht Bielefeld HRA 15344
>
> Persönlich haftende Gesellschafterin:
>
> saltation Beteiligungs-GmbH | Niederwall 43 | 33602 Bielefeld
>
> Sitz Bielefeld | Amtsgericht Bielefeld HRB 39339
> Geschäftsführer: Daniel Brün
>
>