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

Chapter 5. Business Logic

Business logic (also known as the domain logic) is all about the way business wants to handle the data. With this definition, it seems that the Model layer in a Model-View-Controller (MVC) framework could be one of the places to deal with business logic. Forget about MVC because Symfony is more like Request/Response in nature. So, it is your responsibility to create the Model if you need and it is totally up to you how to organize the business logic in your project.

Note

There is a debate about Symfony being an MVC framework. Some developers believe that because entities in Symfony are a data-persistence layer and not a model layer, this makes Symfony a VC framework and not an MVC framework. Sure, you can create Models yourself, but that is where the debate comes from. You have to CREATE them. They DON'T EXIST by default. My thoughts on this? Don't let the terminology trick you. Read about the debates and opposing ideas as much as you can, but at the end of the day...