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

Caches in a Symfony project


In this book, we will focus on two types of caches: the gateway cache (which is called a reverse proxy cache as well) and the doctrine cache. As you may have guessed, the gateway cache deals with all of those HTTP cache headers mentioned in the previous topics. Symfony comes with a very strong gateway cache out of the box. All you need to do is activate it in your front controller, and then start defining your cache expiration and validation strategies in your controllers.

That said, it does not mean that you are forced to use the Symfony cache only. If you prefer other reverse proxy cache libraries (that is, Varnish or Django), you are welcome to use them. The caching configurations in Symfony are transparent so you don't need to change a single line in your controllers when you change your caching libraries. Just modify your config.yml file and you will be good to go.

However, we all know that caching is not for the application layer and views only. Sometimes...