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

Reviewing the facts and building entity relationships


Based on some facts provided in the previous chapter, we have four entities so far: Workspace, Project, Task, and User. Each entity (table) has its own properties (columns) and there is some relationship between these entities. For example, each project can be defined in one workspace only but each workspace can have multiple projects or each task can come from one project only but each project can consist of multiple tasks.

This project is all about task management. So, to visualize it better, imagine that workspace is like a playground for all other entities to deal with tasks, as shown in the following figure:

Currently, we are at the MVP level but as we proceed, the entity structure of the project gets bigger and more complex. So, understanding the whole business logic would be much easier if we create a diagram containing all entities, properties, and relationships.

The best way to create a visual concept from the project facts is to...