Import into Symfony as "symfony/mongodb-messenger"

[GromNaN]

You have done an excellent job with this package. Would you be interested in importing it into symfony/symfony as a messenger bridge and benefiting from greater visibility and support from Symfony contributors?

[Jean85]

HI! Well, I have to say that I'm flattered by this proposal 😄

How this would work? This package is not standalone, it requires the underlying facile-it/mongodb-bundle to work (for the needed MongoDB connection services).

[GromNaN]

Hi! Well, I have to say that I'm flattered by this proposal 😄

I am delighted that you like the idea. This is my initiative and is subject to approval by the core team.

How this would work? This package is not standalone, it requires the underlying facile-it/mongodb-bundle to work (for the needed MongoDB connection services).

If the only dependency is the MongoDB Client connection, it is fairly weak and facile-it/mongodb-bundle will be able to create the transport service itself when the symfony/mongodb-messenger bridge is installed. Otherwise, the connection can be created by the FrameworkBundle or via Doctrine MongoDB ODM as for the Doctrine (ORM) transport: https://symfony.com/doc/current/messenger.html#doctrine-transport

To proceed, we will have to create a PR on symfony/symfony to add the new component. This can be done at the earliest for version 8.1 (we are currently in feature freeze for 7.4-8.0). That gives us six months for this project.

[Jean85]

Yes, the MongoDB connection is the only dependency, but the issue is not getting the service itself but selecting the right one (if there are multiple ones). We would have to define how this would work, since we would have multiple possible sources of connection service.

I would like to maintain compatibility with facile-it/mongodb-bundle, since I have multiple services using both it and this package and no plan to abandon it.

[GromNaN]

I share your concern, there is also the DoctrineMongoDBBundle and an experimental MongoDB bundle that we want to be compatible with the Symfony bridge.

Instead of passing a MongoDB URI, the DSN could be similar to the messenger bridge for Doctrine. It would be mongodb://<connection-service-name>.

connection-service-name would be any Symfony service that is an instance of MongoDB\Client, created by the application or any third-party bundle.

The DocumentEnhancer may be included in the bridge, but probably as a Messenger middleware.

[Jean85]

That makes sense. We could discuss further details in front of code.

What do you need from me now?

[GromNaN]

If you want to start forking symfony/symfony and create the new bridge by copying the structure of other bridges, please do.