Lumen VS DoctrineExtensions

Lumen is also a micro-framework used for developing PHP-powered web applications with 7.6k stars and 1k forks on GitHub. It is based on the Laravel framework and is specifically designed to build microservices and smaller, lightweight applications. The same team behind Laravel creates it and also shares some of its components. But, It is different from Laravel because it doesn’t offer compatibility with any additional Laravel libraries like Cashier, Passport, Scout, etc.

There's a note right in project page:

Lumen

Lumen is a stripped down version of Laravel for building APIs. This makes it a lightweight framework. I'm currently using Lumen in a project and I want to use this opportunity to share some of the things I've learnt.

Official website: lumen.laravel.com

I think there are micro frameworks like lumen that are far more accessible in the first steps (https://lumen.laravel.com).

see also: https://github.com/laravel/lumen

use lumen. it is exactly what you want. https://lumen.laravel.com/

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.