ashwin/nxtgauge-backend-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
11 commits 3 branches 0 tags 1.3 MiB
Find a file
Ashwin Kumar d49a29b965 chore: cleanup — remove stub professionals app, empty crates, unused import 
- Delete apps/professionals (all stub handlers returning mock data, shadowed
  by individual profession services on ports 8085-8093)
- Delete empty crate dirs: crates/config, crates/errors, crates/observability
  (already removed from Cargo.toml workspace members, stale directories)
- Delete empty apps/jobseekers dir (duplicate of apps/job_seekers)
- Remove unused Uri import from gateway main.rs

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-25 23:35:30 +01:00
apps chore: cleanup — remove stub professionals app, empty crates, unused import 2026-03-25 23:35:30 +01:00
crates Align role handlers and shared profession contract updates 2026-03-25 23:03:12 +01:00
docs chore: bootstrap rust backend workspace and migration master plan 2026-03-16 22:23:58 +01:00
scripts fix(seed): align upsert conflict targets with partial unique indexes 2026-03-21 15:17:59 +01:00
.env.example feat(backend): enforce profile approvals and complete migration approval flows 2026-03-19 00:30:23 +01:00
.gitignore feat: add Redis for OTP, auth tokens, rate limiting, lead dedup and marketplace cache 2026-03-18 22:58:42 +01:00
Cargo.toml chore: checkpoint current workspace changes 2026-03-22 15:55:29 +01:00
docker-compose.yml feat: complete rust microservices migration with real db logic 2026-03-17 20:42:51 +01:00
README.md chore: bootstrap rust backend workspace and migration master plan 2026-03-16 22:23:58 +01:00

README.md

NXTGAUGE Backend Rust

Rust migration target for nxtgauge-nov-2025-backend, preserving the same microservices and request flow.

Target Service Topology

  • gateway (HTTP API)
  • users (identity, runtime roles, onboarding, approvals)
  • companies
  • customers
  • professionals
  • jobseekers

Migration Policy

  • Keep contracts stable (REST + proto semantics).
  • Keep runtime-config and onboarding schema behavior unchanged during parity phases.
  • Replace service implementations one by one.

See docs/MIGRATION_MASTER_PLAN.md for full staged plan.