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 to create a service


You don't create services. You create classes and they are already SERVICES if they DO something.

So, the answer to the first question is simple: in reality, you don't need to do anything special to turn an object into a service. It needs only one aspect to be qualified as a service. It simply needs to do something. In other words, if a class contains methods that actually perform a task, you can call the object instantiated from that class a service. For example, Symfony entities are not services because they normally consist of a bunch of property definitions. However, any PHP object that takes these entities and performs some action on them can be called a service.

So, whenever you create a new class, you are potentially creating a new service. Service is just a fancy new name. That's all.