In order for anyone to clone this repo and run on their own environment, there should be a series of immutable and idempotent deployment steps that creates collections with required indexes and sharding strategies (when run against a sharded cluster).
Consider the use of a migrations framework, like Mongo.Migration or mongo-extensions.Migration.
This could also be accomplished with simple naming convention of .js files (i.e. 0_setup.js, 1_indexes.js, etc.) to be executed from the mongo shell.
Which ever path is chosed, it should allow anyone to deploy the Leafsteroids backing database on their localhost (standalone), against a replica set (i.e. Atlas M0) or an Atlas Global Cluster with 2 or more zones with related sharded collections.
Researching and prototyping is needed.
In order for anyone to clone this repo and run on their own environment, there should be a series of immutable and idempotent deployment steps that creates collections with required indexes and sharding strategies (when run against a sharded cluster).
Consider the use of a migrations framework, like Mongo.Migration or mongo-extensions.Migration.
This could also be accomplished with simple naming convention of .js files (i.e. 0_setup.js, 1_indexes.js, etc.) to be executed from the mongo shell.
Which ever path is chosed, it should allow anyone to deploy the Leafsteroids backing database on their localhost (standalone), against a replica set (i.e. Atlas M0) or an Atlas Global Cluster with 2 or more zones with related sharded collections.
Researching and prototyping is needed.