Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

Why is it called a Dependency Injection Container?


You may have noticed that I used Service Container and Dependency Injection Container interchangeably. Based on what we have seen so far, the term Service Container makes sense: we have a couple of services and there is a container that manages them. Right?

However, what does it mean when we say Dependency Injection Container? Who injects what in this definition?

Look at the constructor in the Mava.php class again:

class Mava
{
    private $em;
    public function __construct(EntityManager $em)
    {
        $this->em = $em;
    }
    // ...
}

As you can see, we defined and initialized an EntityManager variable in its constructor and, if you look at the arguments for mava_util in services.yml, you will notice that it is actually a doctrine service called entity_manager:

   mava_util:
      class: AppBundle\Util\Mava
      arguments: ['@doctrine.orm.entity_manager']

So basically, we have injected an entity_manager dependency into our mava_util...