Slim VS Cycle ORM

Slim is a micro PHP framework used for web development with 11.7k stars and 2k forks on GitHub. It has a simple and intuitive API development process. It is a micro-framework, meaning you only get a minimum of support for HTTP requests and forwarding requests to appropriate controllers. So the question is, why should you choose a micro-framework? Because it offers you flexibility and high extensibility.

Slim 4, a minimalistic PHP micro-framework, offers middleware support to easily add CORS headers. Middleware in Slim acts like a series of layers through which your app sends a request. One such layer can be responsible for adding CORS headers.

SlimPHP 3 Skeleton app shows this as well: https://github.com/slimphp/Slim-Skeleton/blob/3.1.8/public/index.php

How hard did you look? There are plenty out there. FastRoute, Phroute, based on FastRoute, with basic middleware, League/Route - routing with middleware, using FastRoute, PSR 7 & 15, Slim Framework, at it's core, it like League/Route, etc. None of these require a full framework to use.

You can have the container call in a config folder with a file called dependencies or how ever you want. A few existing examples of this is here - Slim calls this app/dependencies in this skeleton project and Odan's Skeleton has this as config/container in their project.

Maybe use this if you don't like to dive into bigger frameworks: https://www.slimframework.com/

Go for Slim: https://www.slimframework.com/

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