How datarishavrathore/sms-backend works
This is a small FastAPI student-management API. A client submits student data to the routes in app/main.py; create and update validate it with a Pydantic schema, then query or modify SQLAlchemy student records using a database session. The API also lists and deletes records and exposes a database health check. app/database.py configures the MySQL connection and session lifecycle. The README is empty, so capabilities and relationships here are based on the shown source; no separate deployment or integration workflow is evidenced.
Main entry points: main.py Student routes · database.py DB sessions · models.py Student record · schema.py Student input
Components 6
API
- Student routes
app/main.py
Student data
- Student input
app/schema.py - Student record
app/models.py
Persistence
- DB sessions
app/database.py - MySQL database
Other components
- API client
Connections 7
- API client → Student routes: calls routes
app/main.py - Student routes → Student input: validates input
app/main.py - Student routes → Student record: queries records
app/main.py - Student routes → DB sessions: gets session
app/main.py - Student record → DB sessions: uses base
app/models.py - DB sessions → MySQL database: connects to
app/database.py - Student routes → MySQL database: checks health
app/main.py