[danso]

> We're rebuilding an internal app from scratch and it needs to be blazing fast and real-time.

At risk of dragging the OP into a framework/language war...if you're building an internal app from scratch...why use Symfony? Is it because the rest of the Apple internal apps are in PHP/Symfony and it doesn't make sense to have the internal app group write in different frameworks?

(I'm assuming different languages isn't a huge deal, since the OP mentions using Ruby to handle deployment)

[rramsay]

OP commented here, but didn't respond to you. They most likely went with Symfony since the original codebase was PHP. Porting to Symfony2 gives modern MVC web app framework tools and structure but has the same environment requirements. So there is very little cost as opposed to switching languages. The Ruby deployment methodology most likely uses Capifony a special extension to the Capistrano ruby gem for deployment built around Symfony and Symfony2.