{"repo":"eMAGTechLabs/messenger-mongo-bundle","free":true,"listed":false,"github":"https://github.com/eMAGTechLabs/messenger-mongo-bundle","clone":"git clone https://github.com/eMAGTechLabs/messenger-mongo-bundle.git","description":"A Mongo transport for Symfony Messenger","language":"PHP","stars":16,"topics":["symfony-messenger","mongodb","queue","symfony","messenger-mongo-bundle","transport"],"license":"MIT","category":"chat-messaging","readme_excerpt":"Messenger Mongo Bundle This bundle offers a new type of transport for the Symfony Messenger component. While MongoDB is not the best tool to be used as a queue, sometimes it's more convenient to use the tools that your application already uses. For example, if your application already uses MongoDB and you want a persistent storage for the failed messages, I think it's quite handy to use MongoDB as a storage. Installation The recommended way to install the bundle is through Composer: Configuration & usage Take a look here if you need to find out how to configure the driverOptions , uriOptions and dsn options. The features described here can be used also, therefore the following commands are available in order to manually debug the failed messages: Defining an index for the messages collection The MongoDB collections where messages are stored (default messenger queue ) should have the following index defined: Without the index, the performance may degrade significantly with a large number of items (100k+) in the queue. Submitting bugs and feature requests If you found a nasty bug or want to propose a new feature, you're welcome to open an issue or create a pull request here.","default_branch":null,"files":null,"tree":[],"storefront":"/r/eMAGTechLabs","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/eMAGTechLabs/messenger-mongo-bundle/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}