Login api creation

[anuragp0010]

Let's start with login page and api.

• sign-up
• user name and password
• Driving License and Reg. card
• login and logout

[neeleshyash20]

For starters i have breakdown this product into 3 independent service. The framework i am choosing is Spring Boot with MongoDb and Postgres. (solely Backend)

1. userAuthentication (Including Signup ,login and logout) .This module will contain my Main application from where the Spring boot will run the application
2. BookingService
3. BookingDetails

Entitled To discussion

[neeleshyash20]

1. UserAuthentication Service: This service handles Rider authentication operations such as signup, login, and logout. It serves as the main entry point for your application and runs the Spring Boot application. Utilize Spring Security for implementing authentication and authorization mechanisms. Store Riders credentials securely in either MongoDB or PostgreSQL, depending on your specific requirements. Implement endpoints for Riders registration, login, logout, password reset. implementing JWT (JSON Web Tokens) for stateless authentication and session management.

2. BookingService: This service is responsible for managing booking-related operations. It handles tasks such as creating new bookings, updating booking details, canceling bookings, etc. Implement RESTful APIs for CRUD (Create, Read, Update, Delete) operations related to bookings. MongoDB or PostgreSQL to store booking data, depending on the nature of the data and your scalability needs. (Yet to decide the Specific requirement). Implementing business logic for validating booking requests, managing availability, handling conflicts, etc.

3. BookingDetails Service: This service focuses on retrieving and displaying booking details to Riders. It serves as a read-only service that fetches booking information from the database and presents it to Riders. Implement endpoints for retrieving booking details by ID, listing bookings for a specific user, filtering bookings by date, etc. Use MongoDB or PostgreSQL as the data store, depending on the read requirements and performance considerations. we can consider implementing caching mechanisms to improve the performance of read operations, especially for frequently accessed data.