New Mongodb component standard
Hi! We want to introduce a new standard of mongo component instantiation.
Why?
- It's considered a bad practice, to have one monolithic component containing a collection of connections to every mongodb available on our cloud services. It make things more complex. more complexity means less reliability
- separated and convoluted mongodb configuration make it error prone. currently, mongo option in configuration file, while node address information were stored at traveloka-infra mongo database.
As for new standard guide :
- Every top level component should create it's own distinct component for mongodb consumption purpose
- Configuration for one Mongodb component should be clearly describe everything related to that one mongodb component (e.g cluster hosts, connection options, etc).
For reference of these standards, see :
newer standard -> https://29022131.atlassian.net/wiki/display/BEI/New+procedure+to+use+Mongo+DB+on+your+application
And
migration guide -> https://29022131.atlassian.net/wiki/display/BEI/MongoDB+Component+Migration+Guide
And we kindly ask for coordination from all of us to refactor our component to use newer standard we introduced above.
Thank you 
:bow: