6 Flow of Control

Justin Neilon edited this page 2020-06-22 08:56:12 +02:00

Table of Contents

• Register Flow of Control
• Get Customer Details Flow of Control

The flow of control begins at the controller, moves through the use case, and then winds up executing the presenter.

Register Flow of Control

1. A request is received by the CustomersController then the Post action is invoked.
2. The Post action creates a RegisterInput message then the Register use case is called.
3. The Register use case creates a Customer and an Account entities. Repositories are called, the RegisterOutput message is built and sent to the RegisterPresenter.
4. The RegisterPresenter builds the HTTP response message.
5. The CustomersController asks the presenter for the current response message.

Get Customer Details Flow of Control

1. A request is received by the CustomersController then the GetCustomer action is invoked.
2. The GetCustomer action creates an GetCustomerDetailsInput message then GetCustomerDetails use case is called.
3. The GetCustomerDetails use case asks the repositories about the Customer and the Account. It could call the NotFound or the Default output port of the GetCustomerDetailsPresenter if it exists or does not.
4. The GetCustomerDetailsPresenter builds the HTTP response message.
5. The CustomersController asks the presenter for the current response.

Index of Clean Architecture Manga

Home

• Motivation
  • Learn how to design modular applications
  • Explore the .NET Core features
  • Learn from the open source community
• Contributing

Use Cases

Flow of Control

• Register Flow of Control
• Get Customer Details Flow of Control

Architecture Styles

• Hexagonal Architecture Style
  • Ports
  • Adapters
  • The Left Side
  • The Right Side
• Onion Architecture Style
• Clean Architecture Style

Design Patterns

• Controller
• ViewModel
• Presenter
  • Standard Output
  • Error Output
  • Alternative Output
• Unit of Work
• First-Class Collections
• Factory

Domain-Driven Design Patterns

• Value Object
• Entity
• Aggregate Root
• Repository
• Use Case
• Bounded Context
• Entity Factory
• Domain Service
• Application Service

Separation of Concerns

• Domain
• Application
• Infrastructure
• User Interface

Encapsulation

Test-Driven Development TDD

Fakes

SOLID

• Single Responsibility Principle
• Open-Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• Dependency Inversion Principle

.NET Core Web API

• Swagger and API Versioning
• Microsoft Extensions
• Feature Flags
• Logging
• Data Annotations
• Authentication
• Authorization

Entity Framework Core

• Add Migration
• Update Database

Environment Configurations

DevOps

• Running the Application Locally
• Running the Tests Locally
• Continuous Integration & Continuous Deployment

Docker

• SQL Server

Related Content and Projects