[FLOW3-general] Symfony 2 about to be released.. FLOW3?
Robert Lemke
robert at typo3.org
Mon Mar 14 09:28:52 CET 2011
Hi Stefano,
Am 06.03.2011 um 22:39 schrieb Stefano Cecere:
> i'm about to start a very big new project.. it'll take several months at least to be developed. it'll be more an application/service, than a website
> since it could expand quite big, i don't know if my typical TYPO3 setup + Extbase extensions would support such scalability,
> or FLOW3, or the quite ready Symfony 2 http://symfony.com/
>
> i have to admit that Symfony really wants you to like it, with gorgeous introduction tutorials, english books, proven technologies, successful recent history.
> but as long time (8 years) TYPO3 developer and Association supporter, i'd really prefer to stay TYPO3
>
> SO:
>
> after the (we guess huge) Berlin Code Sprint: what is the status of FLOW3?
as I just wrote in another email to this list, we're currently cleaning up after integrating our two big new features and prepare for the first beta and of course the final 1.0 release.
> is there any real advantage to bet on FLOW3/PHOENIX in 2011? compared to Symfony 2....
> my main concerns are
> 1) docs, tutorials and best practices
The documentation and tutorials of Symfony are just great, they do a good job there.
We plan to updated and complete the FLOW3 documentation for our 1.0 release and I expect that its quality is equally high like that of the Symfony project. A little bird also told me that there will be books being written about FLOW3 ...
As for the best practices: we need to be honest, this is a 1.0 release. So there are not hundreds of projects out there which already use FLOW3 and which we can take as best practices. In that regard you need to see yourself as an early adopter.
However, FLOW3's concept was completely built with a lot of best practices in mind. Sure, we introduced many new practices, such as Dependency Injection, Domain-Driven Design or AOP – but those have been proven to be best practices in other communities already.
As for the practical part: how to secure FLOW3, how to deploy a FLOW3 application – we need to distill what comes out as experiences from the first big projects. Christopher Hlubek (in CC) is working on a big FLOW3 based project since end of last year and might give some advice to you here.
> 2) scalability and performance with huge amounts of data!
If Symfony2 can do it, FLOW3 can handle it as well – we both use Doctrine 2.
Cheers,
Robert
More information about the FLOW3-general
mailing list