https://github.com/deepessh/ecommerce-order-processing

A spring boot based application for order processing. Supports Single/Batch processing. Uses PostgreSQL, Spring Boot, Apache Kafka, Docker. Based on the microservices architecture.
https://github.com/deepessh/ecommerce-order-processing

Last synced: 9 days ago
JSON representation

A spring boot based application for order processing. Supports Single/Batch processing. Uses PostgreSQL, Spring Boot, Apache Kafka, Docker. Based on the microservices architecture.

• Host: GitHub
• URL: https://github.com/deepessh/ecommerce-order-processing
• Owner: deepessh
• Created: 2020-12-04T22:09:46.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2020-12-11T19:17:38.000Z (about 4 years ago)
• Last Synced: 2024-11-09T14:04:26.586Z (2 months ago)
• Language: Java
• Size: 85 KB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# ecommerce-order-processing

The app consists of Spring-Boot based 5 different micro-services, 1 api-gateway service and 1 discovery service.

## Features

1. Uses Netflix Eureka for service discovery

2. Uses Kafka for bulk order processing

3. Uses Swagger OpenApi version 3.0 for API documentation (available at http://localhost:8080/swagger)

4. Unit tests written for item-service, order-service, address-service, payment-method-service

5. Normalized database schema available in Database Schema.xlsx

6. Exposes /orders-bulk endpoint as a client for processing orders in bulk

7. Exposes /orders-bulk/status endpoint as a client for processing order status updates in bulk

All the micro-services are dockerized and deployable to docker using docker-compose.yml file included in the project.

## Prerequisites

1. Java 11

2. Docker

## Steps to run the project

1. execute build_run.sh

## Improvements

1. Logging and metrics can be improved, can use ELK stack to ingest logs and generate metrics

2. Async communication among microservices. Instead of communicating via Http, the microservices can send messages to each other.

3. Unit testing can be improved

4. Integration tests can be added

5. Batch processing servers should be different from normal API servers

6. 

## Bugs

1. Updating bulk status removes items, addresses, payment methods