rwadurian

Commit Graph

Author	SHA1	Message	Date
hailin	2bf5ca933e	refactor(referral): remove legacy leaderboard code Remove duplicate leaderboard functionality from referral-service. All leaderboard features should now go through leaderboard-service. Removed files: - api/controllers/leaderboard.controller.ts - api/dto/leaderboard.dto.ts - application/queries/get-leaderboard.query.ts - infrastructure/cache/leaderboard-cache.service.ts - Related test files Modified: - TeamStatisticsService: removed getLeaderboard() and getUserRank() - Module registrations updated 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2025-12-09 22:05:48 -08:00
hailin	747e4ae8ef	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing - Remove Address field from PartyEndpoint (parties connect to router themselves) - Update K8s Discovery to only manage PartyID and Role labels - Add Party registration and SessionEvent protobuf definitions - Implement PartyRegistry and SessionEventBroadcaster domain logic - Add RegisterParty and SubscribeSessionEvents gRPC handlers - Prepare infrastructure for party-driven MPC coordination This is the first phase of migrating from coordinator-driven to party-driven architecture following international MPC system design patterns.	2025-12-05 08:11:28 -08:00
Developer	7ae98c7f5b	feat(referral-service): Implement complete referral service with DDD architecture Implement the referral service microservice with comprehensive features: ## Domain Layer - ReferralRelationship aggregate: manages user referral relationships - TeamStatistics aggregate: tracks team statistics and leaderboard scores - Value Objects: UserId, ReferralCode, ReferralChain, LeaderboardScore, ProvinceCityDistribution - Domain Services: ReferralChainService, LeaderboardCalculationService - Domain Events: ReferralRelationshipCreated, TeamStatisticsUpdated ## Application Layer - ReferralService: create relationships, get user info, validate codes - TeamStatisticsService: update statistics, get leaderboard, province/city distribution - Commands: CreateReferralRelationship, UpdateTeamStatistics - Queries: GetUserReferralInfo, GetDirectReferrals, GetLeaderboard, GetProvinceCityDistribution - Event Handlers: UserRegisteredHandler, PlantingCreatedHandler ## Infrastructure Layer - Prisma repositories with PostgreSQL - Redis caching for leaderboard - Kafka messaging for domain events - JWT authentication guard ## API Layer - REST endpoints for referral management - Leaderboard endpoints with pagination - Team statistics endpoints - Health check endpoints ## Testing (127 unit + 35 integration + 16 E2E tests) - Domain layer unit tests (100% coverage) - Integration tests with mocks - E2E tests with supertest - Docker test environment with PostgreSQL, Redis, Redpanda 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-12-01 00:18:20 -08:00

Author

SHA1

Message

Date

hailin

2bf5ca933e

refactor(referral): remove legacy leaderboard code

Remove duplicate leaderboard functionality from referral-service.
All leaderboard features should now go through leaderboard-service.

Removed files:
- api/controllers/leaderboard.controller.ts
- api/dto/leaderboard.dto.ts
- application/queries/get-leaderboard.query.ts
- infrastructure/cache/leaderboard-cache.service.ts
- Related test files

Modified:
- TeamStatisticsService: removed getLeaderboard() and getUserRank()
- Module registrations updated

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-09 22:05:48 -08:00

hailin

747e4ae8ef

refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing

- Remove Address field from PartyEndpoint (parties connect to router themselves)
- Update K8s Discovery to only manage PartyID and Role labels
- Add Party registration and SessionEvent protobuf definitions
- Implement PartyRegistry and SessionEventBroadcaster domain logic
- Add RegisterParty and SubscribeSessionEvents gRPC handlers
- Prepare infrastructure for party-driven MPC coordination

This is the first phase of migrating from coordinator-driven to party-driven
architecture following international MPC system design patterns.

2025-12-05 08:11:28 -08:00

Developer

7ae98c7f5b

feat(referral-service): Implement complete referral service with DDD architecture

Implement the referral service microservice with comprehensive features:

## Domain Layer
- ReferralRelationship aggregate: manages user referral relationships
- TeamStatistics aggregate: tracks team statistics and leaderboard scores
- Value Objects: UserId, ReferralCode, ReferralChain, LeaderboardScore, ProvinceCityDistribution
- Domain Services: ReferralChainService, LeaderboardCalculationService
- Domain Events: ReferralRelationshipCreated, TeamStatisticsUpdated

## Application Layer
- ReferralService: create relationships, get user info, validate codes
- TeamStatisticsService: update statistics, get leaderboard, province/city distribution
- Commands: CreateReferralRelationship, UpdateTeamStatistics
- Queries: GetUserReferralInfo, GetDirectReferrals, GetLeaderboard, GetProvinceCityDistribution
- Event Handlers: UserRegisteredHandler, PlantingCreatedHandler

## Infrastructure Layer
- Prisma repositories with PostgreSQL
- Redis caching for leaderboard
- Kafka messaging for domain events
- JWT authentication guard

## API Layer
- REST endpoints for referral management
- Leaderboard endpoints with pagination
- Team statistics endpoints
- Health check endpoints

## Testing (127 unit + 35 integration + 16 E2E tests)
- Domain layer unit tests (100% coverage)
- Integration tests with mocks
- E2E tests with supertest
- Docker test environment with PostgreSQL, Redis, Redpanda

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-01 00:18:20 -08:00

3 Commits