https://github.com/ozturkeniss/microservices-designed
This project implements a modern e-commerce platform using a microservices architecture. The system is designed to be scalable, resilient, and maintainable, following domain-driven design principles and event-driven communication patterns.
https://github.com/ozturkeniss/microservices-designed
aggregator docker e-commerce microservices-architecture ocelot-gateway rabbitmq testing
Last synced: 11 months ago
JSON representation
This project implements a modern e-commerce platform using a microservices architecture. The system is designed to be scalable, resilient, and maintainable, following domain-driven design principles and event-driven communication patterns.
- Host: GitHub
- URL: https://github.com/ozturkeniss/microservices-designed
- Owner: ozturkeniss
- License: mit
- Created: 2025-05-01T00:10:41.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2025-05-02T21:39:03.000Z (about 1 year ago)
- Last Synced: 2025-06-26T10:50:19.239Z (about 1 year ago)
- Topics: aggregator, docker, e-commerce, microservices-architecture, ocelot-gateway, rabbitmq, testing
- Language: C#
- Homepage:
- Size: 49.8 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# E-Commerce Microservices Architecture
## Overview
This project implements a modern e-commerce platform using a microservices architecture. The system is designed to be scalable, resilient, and maintainable, following domain-driven design principles and event-driven communication patterns.
## Architecture
## Service Components
### API Gateways
1. **Ocelot API Gateway**
- Routes external requests to appropriate microservices
- Implements API composition and request aggregation
- Handles cross-cutting concerns like authentication and rate limiting
2. **Aggregator Gateway**
- Provides composite APIs for complex operations
- Orchestrates multiple service calls
- Implements circuit breaker pattern for resilience
### Core Services
1. **Basket Service**
- Manages shopping cart operations
- Implements distributed caching with Redis
- Handles concurrent cart modifications
2. **Product Service**
- Manages product catalog and inventory
- Implements product search and filtering
- Publishes product-related events
3. **Order Service**
- Processes order creation and management
- Implements saga pattern for distributed transactions
- Maintains order history and status
4. **Payment Service**
- Handles payment processing
- Implements payment gateway integration
- Manages transaction history
## Technology Stack
```mermaid
graph LR
A[.NET 8] --> B[ASP.NET Core]
B --> C[Entity Framework Core]
B --> D[Ocelot]
B --> E[Polly]
F[PostgreSQL] --> G[Entity Framework]
H[Redis] --> I[Distributed Cache]
J[RabbitMQ] --> K[Event Bus]
```
### Infrastructure
- **PostgreSQL**: Primary data store for services
- **Redis**: Distributed caching for basket service
- **RabbitMQ**: Message broker for event-driven communication
- **Docker**: Containerization and orchestration
- **Docker Compose**: Local development environment
## Communication Patterns
```mermaid
sequenceDiagram
participant Client
participant Gateway
participant Service
participant EventBus
Client->>Gateway: HTTP Request
Gateway->>Service: Forward Request
Service->>EventBus: Publish Event
EventBus->>Service: Consume Event
Service->>Gateway: Response
Gateway->>Client: HTTP Response
```
### Key Patterns
1. **Event-Driven Architecture**
- Asynchronous communication between services
- Loose coupling and high scalability
- Eventual consistency
2. **Circuit Breaker**
- Fault tolerance and resilience
- Graceful degradation
- Automatic recovery
3. **CQRS Pattern**
- Separate read and write models
- Optimized query performance
- Scalable data access
## Development Guidelines
1. **Service Independence**
- Each service has its own database
- Independent deployment and scaling
- Service-specific technology choices
2. **API Design**
- RESTful endpoints
- Versioned APIs
- Standardized error handling
3. **Testing Strategy**
- Unit tests for business logic
- Integration tests for service communication
- End-to-end tests for critical flows
## Deployment Architecture
```mermaid
graph TD
LB[Load Balancer] --> GW[API Gateway]
GW --> S1[Service 1]
GW --> S2[Service 2]
GW --> S3[Service 3]
S1 --> DB1[(Database 1)]
S2 --> DB2[(Database 2)]
S3 --> DB3[(Database 3)]
S1 --> Cache[(Cache)]
S2 --> Cache
S3 --> Cache
S1 --> MQ[Message Queue]
S2 --> MQ
S3 --> MQ
```
## Monitoring and Observability
- Distributed tracing
- Centralized logging
- Health checks
- Performance metrics
- Alerting system