Our current mechanisms for configuring a MongoClient are:

1. Use a "mongodb://..." style URL
2. Configure a MongoClientSettings object in code

It would be useful to support a JSON based configuration option, where a JSON document could be used to supply the values for the MongoClientSettings.

This could have a number of interesting benefits:

1. It could represent nested values better than a linear URL can
2. Configurations could be built up by merging partial JSON documents that each contain part of the configuration
3. Configurations could be stored in MongoDB

Implementing this feature should be dependent on all drivers agreeing on the format of the JSON configuration document so that configurations can be shared across drivers.