system-architecture
System Architecture
Overview
The Knest Project is designed as a modular, service-oriented system consisting of multiple applications that communicate through a centralized backend.
The architecture separates customer interactions, contractor operations, and administrative management into dedicated interfaces while maintaining a single source of truth for business logic, bookings, payments, and user management.
This modular approach improves maintainability, scalability, and future expansion into additional services and geographic regions.
⸻
System Components
The Knest Project consists of the following primary components:
Customer Mobile Application
Built for customers to:
- Register and manage accounts
- Book cleaning services
- Make payments
- Track bookings
- View booking history
- Leave ratings and reviews
⸻
Contractor Mobile Application
Built for approved contractors to:
- Manage availability
- Receive and manage bookings
- Navigate to service locations
- Verify service scope
- Update booking progress
- Complete jobs
- Track earnings
⸻
Contractor Web Portal
Used exclusively during contractor onboarding.
The portal enables contractors to:
- Register an account
- Complete onboarding
- Upload verification documents
- Submit required information
- Track application status until approval
Once approved, contractors transition to the Contractor Mobile Application for all operational activities.
⸻
Administrative Platform
Provides centralized management of the Knest Project.
The administrative platform manages:
- Customers
- Contractors
- Services
- Pricing
- Bookings
- Payments
- Reviews
- Reports
- Project configuration
⸻
Backend API
The backend acts as the central processing layer for the project.
It is responsible for:
- Authentication
- Business rules
- Booking management
- Contractor assignment
- Payment processing
- Notifications
- Data storage
- Administrative operations
All applications communicate with the backend through secure API endpoints.
⸻
High-Level Architecture
The overall system architecture follows a centralized service model.
Customer Mobile App │ │ ▼ Backend API ─────────── Business Logic Booking Engine Payment Engine Notification Engine User Management ▲ │ │ Contractor Mobile App ▲ │ Contractor Web Portal ▲ │ Administrative Platform
⸻
External Services
The Knest Project integrates with third-party services where required.
These integrations include:
- Stripe for payment processing
- Google Maps services for location and address functionality
- Push notification services
- Email delivery services
The architecture has been designed to allow additional integrations without significant changes to the core application.
⸻
Design Principles
The architecture is based on the following principles:
- Modular application design
- Centralized business logic
- Secure payment processing
- Scalable service architecture
- API-driven communication
- Separation of responsibilities
- Future extensibility
- Maintainable codebase