DoctrineExtensions VS Symfony

In the world of software development, there are two kinds of developers: those who have never had to complain about ORMs and those who have actually used them. Whether it’s Django ORM for Python, Active Record for Ruby, GORM for Golang, Doctrine for PHP, or Prisma for TypeScript, a common issue persists: writing simple queries is straightforward, but constructing complex or optimized queries can take hours, if not days.

The language is not that important, if you know Php, you learn another one in weeks (not you, Rust!) important and source of income is the knowledge of Design patterns and for what implementation to use which specific Pattern. PHP have a great ecosystem regarding design patterns. As there are the psr. Mostly, the Frameworks implement these recommendations: - dependency injection in Symfony, yii and spiral - Data Mapper implemented in doctrine or in cycle-orm.

But: I do know how to filter and paginate 100 million rows under <20ms, in PHP and 1.7GHz laptop. I can do complex data exports at speeds of 15.000 rows per second, where each row takes data from about 5-8 DB tables, and all that using ORM (full entity mapping, the slowest possible way) and not vanilla SQL. And that data is saved sync (not async) to S3 so there is a slowdown that I totally forgot about which means processing is even faster.

Probably the best answer to your question is to use an established "ORM" (Object Relational Mapping). Doctrine ( https://www.doctrine-project.org/ ) is a very popular one. Those libraries have already solved many of the problems you're going to run into.

It is one of the bundles of Symfony, a powerful and flexible PHP framework, also requiring Doctrine ORM entities.

doctrine/* - packages from the Doctrine Project, largely but not exclusively related to working with databases doctrine/collections - utilities for working with arrays of data doctrine/dbal - a data*base **abstraction **l*ayer with support for MySQL, Oracle, Microsoft SQL Server, PostgreSQL, and SQLite databases doctrine/orm - the Doctrine ORM, a popular PHP ORM based on the Data Mapper pattern doctrine/migrations - utilities for database schema versioning (i.e. database migrations)

Symfony Security and Doctrine

ORM is the most known abstraction used to easy access and modify data against SQL databases. Laravel has Eloquent, Symfony has Doctrine, etc.

There are also good ORMs available for PHP. Eloquent and Doctrine come to mind.

Currently Laravel is the "go to" for new PHP applications to mostly developers today, if not, plain PHP, Slim, Symfony and other frameworks does the job, but for Wordpress, custom PHP boilerplates or/and outdated PHP patterns (aka, single ton) is what we have for work in mostly cases, if not, hacky ways to integrate frameworks as Laravel itself or parts of it to leverage a better code structure.

Let's have a look at the class EventSourceHttpClient and try to use it in Symfony\Component\Webhook\Server\Transport. It's an entirely hypothetical example to illustrate the point.

Symfony is an open-source PHP framework developed by SensioLabs which has a thriving community of over 300,000 developers with 29k stars and 9.4k forks on GitHub. It provides a set of reusable PHP components and a development methodology for building complex and scalable web applications. It is recommended due to its advanced features and user-friendly environment. The user can also develop microservices.

Symfony 7

Would be great to see for https://github.com/symfony/symfony, thanks! As that's a monorepo it may provide a challenge to the tool.

As Shopware is mostly based on the Symfony framework, which is in turn based on the PHP language, we should also consider learning about the basics, which will also be useful for other frameworks apart from Shopware, like Symfonycasts, symfony.com, php.net.

Use PHP frameworks such as Symfony. It cares about all the stuff.

Symfony is a PHP framework. https://symfony.com/

It caused much of the internal of Drupal to be re-written. This included how it was extended. With previous major versions you learned about new features and APIs. They followed mostly existing design patterns so it was easy to learn and updates your extensions for. With Symfony you had to learn whole new systems and ways of doing things. It was like learning something entirely new. And, porting extensions to it was far more work and time.

Also, the updates made Drupal slower while consuming far more system resources for the same thing. This increased costs to operate.

Internally, the kernel executes a controller, that is a callable, passing it an array of arguments. For each of these arguments, Symfony calculates its value using services that implement the ValueResolverInterface1.

Drupal is one of the content management systems aka CMS. It has long history and good stability, which is based on PHP and Symfony.