I agree with this proposal. There are risks with creating collections on the fly, with respect to performance. When an application creates a collection, and it begins to grow unbeknownst to operations support teams, issues surface around performance for a collection that support teams were not aware existed. I understand there are use cases where flexibility is required, however MongoDB supports a wide variety of analytical as well as transactional applications across a wide range of industries. In certain transactional systems, the introduction of a new collection – as well as new queries against that collection in the code base – are not possible on the fly in the application layer already, as these require a formal deploy of the application code on the front end side. Quite similarly, there should be a required and accompanying database code deploy that precedes it, which introduces the collection as well as all indexes deemed initially beneficial to support the new application code. This would also ensure the new collection is created in all non production environments as well, as that new code base goes through the SDLC process, and that the number of collections present in DEV, TEST, and PROD are in alignment after the release has fully moved up through each of them and into PROD.