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

So where does the business logic live?


Let's go back to the definition of business logic again. It defines the business requirements and rules that will be applied to the data. This includes the ways data is created, represented, and modified. To give you a short answer, according to our MVP approach, it lives in our AppBundle under the /Entity folder. However, later it will move to a couple of services (which can be kept in any folder and can be called globally from anywhere in the project).

Let me clarify the purpose of using Entity, EntityRepository, and Service in our project. Entity represents an object definition for a thing in real life (that is, workspace, project, task, or user). EntityRepository is where you define methods to do database queries (that is, using CRUD on entities). You can do the same in a Service but the difference is that a Service can be called globally anywhere in your project. Moreover, it is instantiated only once and on demand (no matter how many times you...