.Net 7 Web API Development for Mobile App -- 2
Budget: $30 – $250 USD
Please read carefully the skillsets required before provide offer:
SRS and Figma design will be provided for shortlisted only. So please submit a CLEAR OFFER:
we need API's and backend development for the a Service Platform, here are the key highlighted features, which focus on a microservices architecture, asynchronous programming, and support for technologies like RabbitMQ and MongoDB:
1. Service Requests Management
Request Submission: Users can submit service requests with details such as service type, location, date, and time. The system validates these inputs before submission(Software Requirements S…).
Offer Management: Service providers can view requests and submit customized offers that include pricing and availability. Offers should be managed dynamically and updated in real-time for both parties(Software Requirements S…).
Notifications: Real-time notifications for status updates, offers, and payment confirmations are essential, possibly managed via RabbitMQ for asynchronous updates(Software Requirements S…).
2. User Authentication & Authorization
Role-Based Access Control (RBAC): Implement access control to ensure different roles (customers, vendors, administrators) access only the data and functions relevant to their roles(Software Requirements S…).
KYC Verification: Integrate third-party KYC services for identity checks during service provider onboarding, ensuring compliance with local regulations(Software Requirements S…).
Two-Factor Authentication (2FA): Optional 2FA is recommended for enhanced account security(Software Requirements S…).
3. Payment Processing
Payment Gateway Integration: Secure online transactions are supported through third-party payment providers (e.g., Stripe, PayPal). Payments are held in escrow until service completion(Software Requirements S…).
Booking and Payment Escrow: After booking, the platform should securely hold funds until task completion. This functionality might include asynchronous processing to handle payment confirmation notifications effectively(Software Requirements S…).
4. Geolocation and Proximity Matching
Geolocation Services: Integration with Google Maps or similar services is required for location-based matching, allowing customers to locate nearby service providers(Software Requirements S…).
5. Technology Stack Recommendations
Database: MongoDB is preferred for managing dynamic data structures and handling scalable data processing needs.
Message Queue: RabbitMQ for managing asynchronous processes and real-time notifications, ensuring smooth communication and system performance under load.
Microservices: API development should follow a microservices architecture to enhance scalability, with each feature (e.g., authentication, payment processing, request management) built as an independent service.
SRS and Figma design will be provided for shortlisted only. So please submit a CLEAR OFFER:
we need API's and backend development for the a Service Platform, here are the key highlighted features, which focus on a microservices architecture, asynchronous programming, and support for technologies like RabbitMQ and MongoDB:
1. Service Requests Management
Request Submission: Users can submit service requests with details such as service type, location, date, and time. The system validates these inputs before submission(Software Requirements S…).
Offer Management: Service providers can view requests and submit customized offers that include pricing and availability. Offers should be managed dynamically and updated in real-time for both parties(Software Requirements S…).
Notifications: Real-time notifications for status updates, offers, and payment confirmations are essential, possibly managed via RabbitMQ for asynchronous updates(Software Requirements S…).
2. User Authentication & Authorization
Role-Based Access Control (RBAC): Implement access control to ensure different roles (customers, vendors, administrators) access only the data and functions relevant to their roles(Software Requirements S…).
KYC Verification: Integrate third-party KYC services for identity checks during service provider onboarding, ensuring compliance with local regulations(Software Requirements S…).
Two-Factor Authentication (2FA): Optional 2FA is recommended for enhanced account security(Software Requirements S…).
3. Payment Processing
Payment Gateway Integration: Secure online transactions are supported through third-party payment providers (e.g., Stripe, PayPal). Payments are held in escrow until service completion(Software Requirements S…).
Booking and Payment Escrow: After booking, the platform should securely hold funds until task completion. This functionality might include asynchronous processing to handle payment confirmation notifications effectively(Software Requirements S…).
4. Geolocation and Proximity Matching
Geolocation Services: Integration with Google Maps or similar services is required for location-based matching, allowing customers to locate nearby service providers(Software Requirements S…).
5. Technology Stack Recommendations
Database: MongoDB is preferred for managing dynamic data structures and handling scalable data processing needs.
Message Queue: RabbitMQ for managing asynchronous processes and real-time notifications, ensuring smooth communication and system performance under load.
Microservices: API development should follow a microservices architecture to enhance scalability, with each feature (e.g., authentication, payment processing, request management) built as an independent service.