inQuiry BB has multiple components like assessment-service, flink jobs spread across multiple GitHub repositories. The objective is to decouple the inQuiry specific code from KP (Knowledge-Plaform) Git Repos and bring under inQuiry BB space in GitHub.
Current Code Structure:
github.com/project-sunbird/knowledge-platform
/knowledge-platform/assessment-api (assessment-service specific code)
/assessment-api/ assessment-service (play application)
/assessment-api/ assessment-actors (actor implementation)
/assessment-api/ qs-hierarchy-manager (hierarchy-manager)
/knowledge-platform/ontology-engine (assessment-service uses entire ontology-engine)
/ontology-engine/graph-common
/ontology-engine/graph-core_2.11
/ontology-engine/graph-dac-api
/ontology-engine/graph-engine_2.11
/ontology-engine/parseq
/knowledge-platform/platform-core (assessment-service uses entire platform-core directly or via ontology-engine)
/platform-core/actor-core
/ontology-engine/schema-validator
/ontology-engine/platform-telemetry
/ontology-engine/platform-common
/ontology-engine/platform-common
/ontology-engine/cassandra-connector
/ontology-engine/kafka-client
/knowledge-platform/platform-modules (assessment-service uses only import-manager module)
/platform-modules/import-manager
/platform-modules/mimetype-manager
/platform-modules/url-manager
github.com/project-sunbird/knowledge-platform-jobs
/knowledge-platform-jobs/jobs-core (common module for all flink jobs)
/knowledge-platform-jobs/auto-creator-v2 (inQuiry BB job)
/knowledge-platform-jobs/publish-pipeline
/publish-pipeline/publish-core (common module for other publish job)
/publish-pipeline/questionset-publish (inQuiry BB job)
Dependency with Knowlg BB:
Currently all common modules are part of knowlg BB and tightly coupled with knowlg/inQuiry services/jobs.
Open Questions:
0 Comments