A framework is a set of libraries that a certain technology makes available to us to solve common problems that usually appear in the development of web applications. That said, what’s wrong? Symfony making it productive as a framework? Here I show six sections that give us a general idea.
Symfony Is A Versatile Framework
There are various types of switchgear on the market. Those compact, very “monolithic” stacks are similar to CakePHP. Others are based on components like Zend, and there are also very light mvc frameworks for small applications like Fuel. Symfony can work like any of these.
We can configure it as a complete set: Twenty-one standalone components plus various external libraries such as Doctrine and self-developed and third-party bundles. But we can also use only some of its members or even the smallest and lightest version of this framework, Silex, which has only one file.
ALSO READ: What Is A Framework? And Its Types
Symfony Is Very Useful
Virtually all web applications have to solve common problems like user access, credential security if we have different types of roles in them, forms, data persistence, internationalization, etc. Sinfonia solves these repetitive problems simply, saving us time in development. It offers us a set of tools that allow us, as developers, to focus on the logic of our application and not on these problems that are already solved. We don’t have to reinvent anything that has already been invented.
Bundle: Essential Feature In Programming
Symfony has another very important feature which is bundles. These are exclusive features that we can reuse in other applications easily. This allows us to reuse our code for similar needs in applications with few changes. Not only does it allow us to create our features, but we can also use others made by third parties. A large catalog of bundles indicates their purpose, reliability and maintenance. Bundles are something like WordPress plugins.
Compile Good Practices Used In Other Frameworks
This innovative system has developed ideas about the best of other frameworks in the market and merged them into one. So he took cues from:
It’s A Flexible Framework
It is very flexible in the application’s configuration and in the use of the templates. This means that we can work with different formats. Therefore, other developers will be able to develop the application in the most comfortable form. For example, to configure the application, we can do it via YAML, XML or PHP files.
We can do the same with templates. What? Using Twig as the engine to make them. It is easy, comfortable and powerful to use, but if we feel more comfortable developing them in PHP, there is no problem. This idea can also be extended to databases. We can use SQL storage like MySQL, SQLServer, Oracle and noSQL storage like MongoDB.
Support: A Key To Successful Performance
Fortunately, the system we are dealing with has many support tools. On the one hand, there is extensive documentation, from the official books we can get in pdf to the communities of this framework, where we will find forums with updated information in both English and Spanish. In the link section of interest, I show some of them. Therefore, we can summarize that it is a productive framework due to its flexibility.
It allows us to solve repetitive tasks very easily because it will enable us to create our features (bundles) that we can reuse in other applications or use third-party bundles because it brings together a picture of the best of many and because the support for our work is broad.