FoodCart - Food Delivery App(Spring Boot)

FoodCart is a cutting-edge online food delivery platform designed to bridge the gap between passionate food enthusiasts and diverse dining experiences. Whether you’re a restaurant owner looking to expand your reach or a foodie searching for the perfect meal, FoodCart offers a seamless, intuitive, and secure environment for everyone. With its robust multi-vendor system, tailored admin panels, and user-friendly features, FoodCart redefines the online dining experience, making it not just a service, but a community.

Live Demo | API Documentation(Swagger)

http://foodcart-env.ap-south-1.elasticbeanstalk.com/swagger-ui/index.html

Key Features:

• Multi-vendor Support: A diverse marketplace where multiple restaurants can register and showcase their menus, offering users a wide range of dining options.
• Tailored Admin Panels: Restaurant owners get a specialized admin panel to manage their listings, orders, and events, while the platform owner benefits from a comprehensive super admin panel.
• Role-based Access Control: Securely manage different user roles (admin, restaurant owner, customer) ensuring a controlled and safe environment.
• User-friendly Functions: Enhance user experience with features like ‘Add to Favorite,’ ‘Add to Cart,’ ‘Remove from Cart,’ and more.
• Secure Transactions: Integrated with Stripe for secure payment processing, along with strong authentication and password management practices.
• Event Notifications: Restaurants can create and promote events, with customers receiving timely email notification.
• Review System: Empowering both restaurant owners and customers to provide and view ratings and feedback.

Security Features:

• Authentication: JWT tokens are used for secure authentication and session management.
• Authorization: Role-based access control is implemented to manage permissions, ensuring that only authorized users can perform specific actions.
• Data Encryption: Sensitive data, including passwords and payment details, is encrypted to protect user information from unauthorized access.

Technologies Used:

• Back-End: Spring Boot, Spring Security, Spring Data JPA
• Database: MySQL
• Payment Gateway: Stripe
• Authentication: JWT, Spring Security
• Deployment: AWS
• Notifications: Email notifications for events and order updates

Project Description:

Controllers:

• Restaurant Controller: Handles actions related to restaurants, including fetching details, searching, and adding favorites.
• Cart Controller: Manages user carts, including adding items, updating quantities, clearing the cart, and calculating the total.
• Admin Restaurant Controller: Provides administrative functions for managing restaurants, including creating, updating, deleting, and changing status.
• Admin Order Controller: Allows administrators to manage orders, including changing status, retrieving orders by restaurant, and deleting orders.
• Admin Menu Item Controller: Allows administrators to manage menu items (food) by creating, updating, deleting, and searching.
• Ingredients Controller: Provides administrative functions for managing ingredients, including adding, updating, deleting, and managing stock.
• Auth Controller: Handles user authentication using JWT token for login and signup.
• Review Controller: Manages customer reviews, allowing posting, fetching, and deleting.
• Order Controller: Handles order creation and retrieval by user.
• Event Controller: Allows administrators to manage events for specific restaurants, including adding, retrieving, and deleting events.
• Category Controller: Provides functions for managing food categories, including adding and fetching categories for a specific restaurant.
• User Controller: Allows fetching user profile information.
• Super Admin Controller: Provides administrative access for managing pending customers and customers.
• Payment Controller: Handles payment success notifications for orders.
• Notification Controller: Provides functionality to fetch notifications.
• Menu Item Controller: Allows fetching menu items (food) by search and restaurant.

Database Diagram

The database diagram shows the entities and relationships within the system:

• User: Represents users of the system with details like name, email, and role.
• Restaurant: Stores information about restaurants, including details, ratings, address, and opening hours.
• Category: Represents categories for menu items (food).
• Food: Represents menu items, including details, availability, and category.
• Ingredients: Stores information about ingredients used in the menu items.
• Cart: Represents a shopping cart associated with a user.
• Cart Item: Contains details of items in the user's cart.
• Orders: Contains details about placed orders, including items, status, and customer information.
• Order Items: Details about items included in an order.
• Payment: Records payment information related to an order.
• Review: Stores customer reviews for restaurants.
• Event: Represents events associated with a specific restaurant.
• Notification: Stores notifications for users.
• Address: Stores address details for restaurants and users.
• User Entity Favorites: Represents user's favorite restaurants.
• Food Images: Stores images related to menu items.
• Restaurant Images: Stores images for restaurants.

Database Relationships:

One-to-many relationships exist between:

• User and Restaurant (user can have multiple favorite restaurants)
• User and Cart (user can have a single cart)
• Restaurant and Food (restaurant can have multiple food items)
• Food and Ingredient (food can have multiple ingredients)
• Food and Food Images (food can have multiple images)
• Restaurant and Restaurant Images (restaurant can have multiple images)
• Order and Order Item (order can have multiple order items)
• Restaurant and Event (restaurant can have multiple events)
• Restaurant and Category (restaurant can have multiple categories)
• Order and Payment (order can have one payment)
• User and Notification (user can have multiple notifications)

Many-to-many relationships exist between:

• User and Address (user can have multiple addresses and one address can be shared by multiple users)
• User and Restaurant (user can be associated with multiple restaurants and a restaurant can be associated with multiple users)
• Food and Ingredient (food can contain multiple ingredients, and an ingredient can be used in multiple foods)

Why I Created This Project:

FoodCart reflects my passion for coding and my commitment to developing practical solutions that can have a positive impact on users' daily lives. It’s a project that merges my technical skills with my enthusiasm for solving real-world problems in the food industry.

Getting Started:

Prerequisites:

• Java 17+
• MySQL
• Maven
• AWS Account

Installation and Setup

1. Clone the repository to your local computer.

  git clone https://github.com/avijit18/FoodCart

2. Navigate to the Project Directory

  cd foodcart

3. Set Up Stripe API:

• Login to Stripe offical website or Sign-up for new account.
• Once logged in, navigate to the Dashboard. This is where you can manage your Stripe account, view transactions, and access your API keys.
• On the left sidebar, go to Developers > API Keys. Here, you'll find your Publishable key and Secret key.
• Copy the Publishable key and Secret key. The Publishable key is used for client-side requests, while the Secret key is used for server-side requests.

In the application.properties Add your Secret API key

stripe.api.key=YOUR_API_KEY

4. Configure the Database:

• Set up a MySQL database.
• In the application.properties update the properties as needed.

spring.datasource.url=jdbc:mysql://localhost:3306/your_database_name
spring.datasource.username=root
spring.datasource.password=your_password

5. Access FoodCart:

  Open your browser and go to http://localhost:8080

Deployment:

The FoodCart application is fully deployed on AWS, ensuring a robust and scalable environment to handle production-level traffic. Below are the key aspects of the deployment and how you can explore the live application.

AWS Deployment:

• AWS Setup: The application is hosted on AWS, utilizing services such as EC2 for server instances, RDS for the database, and S3 for static file storage. The deployment process involved setting up a secure and scalable environment, ensuring high availability and reliability.
• Swagger Documentation: To explore the API endpoints and interact with the backend services, visit the Swagger documentation.

Contribute:

Feel free to contribute to this project by submitting issues, suggesting features, or creating pull requests. Your input is valuable to make this tool even better! 😃

Planned Future Enhancements:

• Password Reset via Email: Implementing a secure and convenient method for users to reset their passwords through email.
• UI/UX Improvements: Introducing a responsive and visually appealing frontend interface to complement the backend functionalities.
• Event Feature Enhancements: Expanding the event creation and management capabilities, allowing restaurants to offer more dynamic and interactive experiences. Future updates will include more detailed event descriptions, customizable notifications, and user engagement tracking.
• Review System Enhancements: Improving the review and rating system to include more granular feedback options, verified reviews, and sentiment analysis. This will provide more accurate and meaningful insights for both restaurants and customers.

Feedback

I appreciate your feedback! Please open an issue on GitHub if you encounter any problems or have suggestions for improvement. Your feedback helps enhance the project for everyone. Please reach out to me at [email protected]

Authors

• @Avijit Patra

Swagger Images

Demo

food_cart_demo1.1.mp4

food_cart_demo2.1.mp4