OVB.Demos.Ecommerce

About the author

The author, Otávio Villas Boas Simoncini Carmanini, sought to create this repository to reproduce the knowledge acquired throughout his development process, as well as to apply discussions and trade-off's discussed in mentoring coordinated by Marcelo Castelo Branco. It is worth remembering that this repository seeks to clarify as much as possible questions that can occur about the development project, so that it has an analytical character regarding data modeling, componentization of microservices, the use of certain standards and their relationships with functional and non -functional requirements.

Thus, throughout this Wiki, I will seek to put different views and solutions to the same problem, as well as obtain factual data to choose certain non -functional processes.

? Project objective

The purpose of this project is to apply the main concepts used together the architecture of microservices, as a way of understanding and aiming at the real reasons for using each standard in order to understand what their consequences are and what they have to offer best. It is noteworthy that the idea is to explain what , why , the purpose and the consequence .

How to run the project

Prerequisites

• .NET 7 SDK installed.
• Docker installed.
• Basic knowledge of docker and c#/. Net

Run

To run the project, first, it is necessary to clone the project on your machine to be able to run external facilities and applications:

 git clone https://github.com/otaviovb/ovb.demos.ecommerce

After running the project, enter the solution folder:

 cd OVB.Demos.Ecommerce

With the open solution folder, start running the Docker Composis to implement the necessary facilities:

 docker compose up -d

? Author

Otávio Villas Boas Simoncini Carmanini

Technologies used

• ASP. Net Core 7
• .NET 7
• Entity Framework Core 7
• Postgree sql
• Postgree Admin
• Open Telemetry
• Jaeger
• Prometheus
• Rabbitmq
• Docker/Docker-Compose
• grpc

Applied concepts

• MULTTENANT
• Repository Pattern
• Adapter pattern
• Notification Pattern
• Builder Pattern
• Unit of Work Pattern
• Singleton Pattern
• Command Handler Pattern
• Command Pattern
• Database Transactions
• Microservices Architecture
• Architecture In Layers
• Rich Domain
• Orchestration Services
• Choreography Services
• Solid Principles
• Dependency Injection
• Async Operations
• Continous Deployment/Continuous Integration
• Data page
• API Versioning
• Messenger
• Health Checks
• Eventual consistency
• Command Query Responsibility Segregation (CQRS)
• Retry pattern
• Resilience policies
• Circuit Breaker Pattern
• Protobuf binary serialization (FASTER THAN JSONSERALIZER OR OHER LIBRARIES)
• Worker Services
• GRPC Communication Services
• Observability: Trace
• Observability: Metrics
• Open Telemetry Collector Agent
• API GATEWAY
• Domain Driven Design
• Unit Tests
• Integration Test