How lokesh15553/doctor-appointment-app-smartbridge_intern_project works
Project Type and Purpose
• This is a full-stack web application (“Doctor Appointment App”) that lets patients and doctors book, reschedule, cancel, and track medical appointments via a responsive UI.
• Key use cases: user authentication (doctor & patient), real-time slot availability, email notifications, medical history tracking.
File Structure
• Top-level folders:
• Document/ (documentation artifacts)
• Project files/Backend (server code)
• Project files/Frontend (client code)
• Video doc/ (demo video)
• README.md at root describes overall app; Project files/Readme.md likely contains setup for code; Backend and Frontend directories indicate a clear separation of concerns.
• No monorepo; classic multi-repo style grouped in Project files/.
README for Additional Insights
• Frontend tech: React (JS/CSS/HTML)
• Backend tech: Node.js (or alternately Django/Flask)
• Database: MongoDB/MySQL/PostgreSQL
• Auth: JWT/Firebase/OAuth
• Email notifications via SMTP or third-party (e.g., SendGrid)
• Deployment targets: Vercel/Heroku/Render
Main Components and Their Relationships
a. Frontend (Web & Mobile-friendly React App)
• UI screens: login, search doctors, booking calendar, history.
• Interacts with Backend APIs over HTTPS (REST or GraphQL).
b. Backend API Server (Node.js)
• API Gateway / Router
• Auth Service (JWT issuance & validation)
• Appointment Service (CRUD endpoints for bookings)
• Doctor Service (search by specialization/location)
• Medical History Service
• Notification Service (push email tasks to message queue)
c. Database
• Primary datastore (e.g., MongoDB collections or SQL tables)
• Stores users, doctors, appointments, medical records.
d. External Services
• Email provider (SMTP, SendGrid, SES) for notifications
• (Future) Calendar sync APIs (Google/Outlook)
• (Future) Payment gateway
e. Optional Infrastructure
• Redis or another in-memory store for caching slot availability.
• Message broker (RabbitMQ/Redis Streams) to decouple notification jobs.
Architectural Patterns and Design Principles
• Separation of concerns: distinct frontend & backend repos.
• Micro-service–like modules within the backend for each domain (Auth, Appointment, Notification).
• Stateless APIs with JWT for horizontal scaling.
• Message queue for asynchronous tasks (email sending).
• Responsive UI – single page application (SPA) pattern.