Minutes of discussions
The first meeting was held to decide the technologies to be used.
- Python service will be used as gateway which will communicate with the UI and other microservices.
- A java service will be used as a queue worker which will take tasks from a queue and then retrieve this data from AWS to push to the database.
- A nodejs service will be used to communicate with the database. All requests for the database will go through this service.
- RabbitMQ will be used as a queue service.
- Mongodb will be used as the database.
- Reactjs will be used for the UI.
- Another python service will be used for logging.
The second meeting was held to divide tasks between members.
- Pranav will take the Java service which will be queue_worker and data_extractor.
- Rishabh will work on the Nodejs service for the database and Reactjs for frontend.
- Tanmay will work on the API gateway along with the logging service in Python.
The third meeting was held to discuss progress and data.
- Everyone worked together to figure out how to extract data from the files received from AWS bucket.
- Mapping tool in Reactjs was decided.
- Idea to use docker for deployment was introduced.
- All endpoints were defined for all microservices.
The fourth meeting was held to discuss progress and documentation.
- Documentation standards were set.
- Integration testing methodology was discussed.
- Tweaks in the endpoints were made.
- Napkin diagram was proposed by Rishabh.
- Logging service was set to the lowest priority.
The fifth meeting was held for integration testing and deployement.
- Docker was used to deploy the project.
- All technology versions were defined.
- Some tests were run on a zoom call.
The sixth meeting was held for documentation.
- Git Wiki entries were discussed.
- Small bugs were fixed.