How elmir-ahmed/triqna works
Triqna is documented as a microservice ridesharing platform with JWT authentication, a gateway, and separate booking and ride services. The available source excerpts show service startup, controller mapping, health endpoints, and auth security rules, but not booking or ride business logic, gateway routing, or service-to-service calls. The React client is mentioned in the README but has no source directory in the supplied tree, so it is represented as an external initiating actor.
Main entry points: bookings-service/Program.cs Bookings service · rides-service/Program.cs Rides service · triqna-gateway API gateway · HealthController.cs Bookings health endpoint
Components 9
Platform entry
- API gateway
apps/triqna-gateway
Backend services
- Bookings service
apps/bookings-service/Program.cs - Bookings health endpoint
apps/bookings-service/Controllers/HealthController.cs - Rides service
apps/rides-service/Program.cs - Rides health endpoint
apps/rides-service/Controllers/HealthController.cs
Authentication
- Auth service
apps/auth-service/src/main/java/com/triqna/auth_service/AuthServiceApplication.java - JWT security rules
apps/auth-service/src/main/java/com/triqna/auth_service/config/SecurityConfig.java - Auth health endpoint
apps/auth-service/src/main/java/com/triqna/auth_service/controller/HealthController.java
Other components
- Rider / client
Connections 3
- Rider / client → API gateway: sends requests
- Bookings service → Bookings health endpoint: maps controllers
apps/bookings-service/Program.cs - Rides service → Rides health endpoint: maps controllers
apps/rides-service/Program.cs