Cycle ORM VS di

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).

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.

Version released.

Now that we are clear about the concepts of configuration, container di and factory, let's see the complexity of creating an app.

Using the container di: Usage of the container di is fairly simple: You first initialize it with an array of definitions. The array keys are usually interface names. It will then use these definitions to create an object whenever that type is requested. This happens for example when fetching a type directly from the container somewhere in the application. But objects are also created implicitly if a definition has a dependency to another definition.

Now that we understand the concept in our next post, we will fully describe our configurations, and explain in detail the use of the container di and the factory.

Yii Dependency Injection 1.0.0