What to use - xPDO or doctrine in a highload project?

Question

PHP

- many entities
- Large system of roles
- a large number of requests and users
In a nutshell, a large CRM.
Now written in yii 2 - server part aka rest api.
Front-end separate web client.
I sit and look at the whole thing from the outside, and I feel that I may have to refactor what has already been written.
Well, symfony, but is doctrine really necessary?
As I can see.
- xPDO: there is a generation of map classes from xml , there is a generation of xml schemas of entities in the database into map classes.
Used in modx revolution.
Essentially a wrapper on PDO. It is possible to write your own PDO dev utils which thread for bottlenecks and share with xPDO.
Roles: own implementation or integration of something third-party according to the ACL pattern.
Http stack: symfony http foundation, in my opinion everything is there, including StreamedResponse.
The doctrine is a step forward, these are migrations, a lot of goodies for the collective development of a complex CRM system. But is such a combine necessary?
Who has experience, how can you comment on my list of approaches? What else can you add?

Answer 1

Look towards apigility, it is based on zend framwork.
Apigility + Doctrine was used in one of the complex APIs