Oops!! Symfony was a pain when I did my first project on Symfony. But now I think I am fortunate that I have done a project on Symfony when I got the announcement that Drupal will adopt some of the Symfony Components.
Not about some minor components, they are embracing Symfony's vision and they will use the major components that will allow them to build a great low-level architecture for Drupal 8: HttpFoundation, HttpKernel, Routing, EventDispatcher, DependencyInjection, and ClassLoader.
I was on a Classic CRUD Application with Symfony and trust me developing classic CRUD application (Creating/Reading/Updating/Deleting) working with data bases is a pretty typical task. Still, I would have Symfony2 has a very handy set of console commands for generating various elements. Using them will save you a great deal of time. Creating Bundle -> Meta Data -> Creating Entity thease are few basic steps need to build up the architecture. Symfony shares some of the concepts of the MVC pattern--such as layer separation--the main goal of the framework is to return a response in a optimized and effective way.
As I said you above, Drupal is not using Symfony as a full stack framework. Like ClassLoader Provides tools to autoload your classes and cache their locations for performance. Whenever you reference a class that has not been required or included yet, PHP uses the autoloading mechanism to delegate the loading of a file defining the class.
I will wait for you to discuss on your requirem