Fix the GitHub folder structure and code organisation

satendrapalsingh commented 2 years ago

[ ] 01. Refactor the folder Structure in GitHub -Update: Review is pending
[ ] 02. Review code organisation with Anand P. Code review can happen only after some basic organisation. - Update: Review is pending
[ ] 03. Create the separate repositories for each layer (Decoupling of the layers). New repositories already created. Update read-me for each repository. Utilities and properties related stuff could be moved to the util directory. This will enable us to deploy each of the components independently (microservice architecture). Today it is a monolith with everything being deployed at once - there is no choice to the adopter. - Update: Required inputs on when to do
[ ] 04. Any method should not be more than 5-10 lines. Current code is 1500 lines. That’s so difficult to maintain and contribute to. (See https://github.com/Sunbird-cQube/cQube_Workflow/blob/release-3.7/development/datasource/python/config_create_table_params.py) - Update: Refactoring is partially done.
[ ] 05. Keep the cQube 3.7 repository until the bugs are fixed. Later on make a note in the Readme.txt file with the new repository. Lock old repositories and start using new ones.
[ ] 06. Add comments to the code. - Update: Is there sunbird specific standard we need to follow or how do you suggest
[ ] 07. Question: How can we change the orchestration engine (say, NiFi with Airflow), database (say, Mongo instead of Postgres), and cloud service provider (Azure instead of AWS)?

RNarmatha commented 1 year ago

@ananya-jain1 Please look into this ticket

ananya-jain1 commented 1 year ago

@htvenkatesh - please consider these practices as part of the cQube roadmap. Let's incorporate in the next 2 sprint plans.

Sunbird-cQube / community