How katragadda-bharath/exacker works
Exacker is a farm-management API backed by SQL Server, with a browser-facing entry point and endpoints for groups, lands, workers, expenses, and payments, plus custom-query execution. The evidenced request flow is HTTP routing through controllers and services to repositories and SQL Server; sampled code confirms the query and payment data paths. Other entity modules appear in the tree, but their internal calls were not sampled, so those links are omitted.
Main entry points: Database SQL Server · database.js DB connection · server.js Express server · services Services
Components 16
Entry points
- Web page
frontend/pages/index.html - Express server
backend/src/server.js
API layers
- API routes
backend/src/routes - Controllers
backend/src/controllers - Services
backend/src/services - Query repository
backend/src/repositories/query.repository.js - Payment repository
backend/src/repositories/payment.repository.js - Farm repositories
backend/src/repositories
Farm data
Persistence
- DB connection
backend/src/config/database.js - SQL Server
Documents/Database
Other components
- Farm user
Connections 18
- Farm user → Web page: uses
- Farm user → Express server: sends requests
- Express server → API routes: dispatches
- Express server → DB connection: checks connection
- API routes → Controllers: dispatches
- Controllers → Services: calls
- Services → Query repository: calls
- Query repository → DB connection: gets pool
- Query repository → SQL Server: executes query
- Services → Payment repository: calls
- Payment repository → DB connection: gets pool
- Payment repository → SQL Server: executes procedures
- DB connection → SQL Server: connects
- SQL Server → Groups: stores
- SQL Server → Lands: stores
- SQL Server → Workers: stores
- SQL Server → Expenses: stores
- SQL Server → Payments: stores