How elevate-project/samiksha-service works
Project type and purpose
• This is a full‐stack Survey & Observation application (“Survey Service”) comprising:
• A Node.js/Express‐based backend microservice (app.js)
• An Angular frontend (samiksha-ui-2)
• Multiple supporting microservices (entity-management, user, notification, interface, scheduler) referenced in setup docs
• Infrastructure components: PostgreSQL (Citus), MongoDB, Cassandra, Elasticsearch, Redis, Kafka/Zookeeper, cloud file storage
File structure
• Top‐level backend folders:
• config: environment and infrastructure configs (DB, Kafka, cloud storage)
• controllers/v1,v2,v3: HTTP API handlers (REST endpoints)
• module: domain logic split by functional area + validation helpers
• models + databaseQueries: ORM models and raw queries (Postgres, Mongo)
• generics: cross‐cutting helpers (file upload, Kafka producers/consumers, middleware, services to other microservices)
• healthCheck: readiness probes for each external component
• routes/index.js: Express router setup
• Frontend: samiksha-ui-2 (Angular app) under a separate directory
• Deployment and docs: Dockerfile, docker-compose.yml, ansible.yml, scripts for Dockerized & native installs
• External dependency definitions: .env.sample for Survey and samples for other services
Read README for additional insights
• Service exposes REST endpoints for creating/consuming surveys, observations, reports
• Communicates with other ELEVATE microservices via HTTP (via generics/httpRequest helper) or Kafka (via generics/kafkaCommunications)
• Data persistence in multiple stores:
• Postgres (user, core survey structures, relational data)
• MongoDB (forms, profiling configs imported via scripts)
• Cassandra & Elasticsearch for high‐volume or search use cases
• File storage through cloud gateways (AWS, GCP, Azure)