phpstan-strict-rules VS DoctrineExtensions

Want even more strictness? The phpstan-strict-rules extension adds additional rules for defensive programming, including stricter array handling and more aggressive type checking.

https://github.com/phpstan/phpstan-strict-rules has a rule disallowing empty. I like the rule and although I haven't used this ruleset I try to avoid using empty in PHP.

phpstan has some strictness rules which, at a glance, can cover this: https://github.com/phpstan/phpstan-strict-rules/blob/1.2.x/README.md

The domain is, basically, the part of your code which defines what the project actually does. For instance, when you persist an entity to the database, your domain is not in charge of persisting it on the database, but making sure that the persisted data makes sense according to your business model. Possibly, when you save your data on the database, you will use an external library like PHP Doctrine. This library is already fully tested, there is no need to test what it does. If you pass to doctrine the correct data, it will be saved to the database with no issues.

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.