Architecture dilemma to separate api project and job project with Symfony / Doctrine [closed]

  architecture, doctrine, orm, symfony

I have a question about architecture.

My devops team wants to make one project = one deployment, but they also want to separate api project from job project (only containing commands). It’s easier for other team because they don’t use an ORM nor Symfony, but for my team I have a dilemma with entities, repositories and migrations.

In order to keep a good development & deployment flow, what do you think ? do I need to remove the ORM ? create a vendor containing only entities/repositories/migrations to share between api and job project ?

Thanks if you have any ideas

Source: Symfony Questions