Implement Order UseCase: Create-Order, Case 1

Context

we made preparations and now time for first business flow implementation
Take a look on 1-documentation/business/order/Create-Order.md for general overview of flow
Remember about SOLID, KISS, DRY, OOP, Hexagonal Architecture
Remember about Reactiveness
Remember that database, warehouse, payment, delivery services return the Flux/Mono objects

Acceptance Criteria

Defined interface for communication with Database (not implementation!)
Defined only necessary methods for communication with Database in scope of task
Defined interface for communication with Warehouse, Payment, Delivery Services (not implementation!)
Implemented Order Duplication functionality (consider using GoF patterns, e.g. Chain of Responsibility or Strategy)
Implemented Order Correctness functionality (consider using GoF patterns, e.g. Chain of Responsibility or Strategy)
Partially implemented Create Order UseCase: Case 1 (without database, other services communications)
Covered with unit tests: UseCase, Order Duplication, Mappers
Defined Order Duplication UML Diagram that explains how works order duplication mechanism
Implemented all mapping through Mapstruct
Fell free to add any DTOs that improve readability

Technical Details

Be align with Testing Agreement described in Working-Agreement.md
Be align with Common Architectural Agreement described in Working-Agreement.md
Be sure of using StepVerifier for reactive unit test (https://medium.com/digitalfrontiers/step-up-your-reactive-tests-with-the-stepverifier-126654fbcdef)

sokimaaa / 6Core