partitionable VS Cycle ORM

From the same developers :

PHP framework : https://spiral.dev/

ORM library : https://cycle-orm.dev/

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.

Either use PDO directly, use Doctrine DBAL (not ORM) or if you need an ORM, check out Cycle ORM which is completely dynamic and supports configuration on-the-fly.

Doctrine is my preferred ORM, being both powerful and battle-tested. There's a relatively new one lately called Cycle but I don't know anything about it other than that it's also a datamapper like Doctrine. Looks pretty decent from the docs tho.

It uses the (H)MVC model, anti-leak DI container, DataMapper ORM (https://github.com/cycle/orm), Symfony components, and RoadRunner (https://github.com/spiral/roadrunner) as an app server (which we also created).