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

How are services beneficial to our projects?


If we are creating services in our professional lives (without realizing it), then why don't we feel any difference in our codes?

This is because classes are the body of a service. Without their souls, they are simply another PHP object. Their soul is the concept that gives them birth by instantiating them only if they are needed.

The Dependency Injection Container (or Service Container) is such a concept. It manages the instantiation of services on demand. This means that the service container constructs and returns them once if they are requested. This utilizes memory and application performance in two ways:

  • If you create a service but never use it, no memory will be wasted for instantiation

  • If you create a service and use it multiple times, memory will be allocated for the size of one instance only and will be shared across all the instances

This is powerful. Imagine the memory saved in this way.

What if we needed a unique instance of a service?...