4.1 - youtube tutorials (AxonIQ#92)

* Adding the Youtube guides

 - part 3: The Command Model
 - part 4: The Query Model

* Adding the Youtube guides

Renaming of links

configuring-infrastructure-components/messaging-concepts/messaging-concepts.md

@@ -6,7 +6,7 @@ Although all these messages implement the `Message` interface, there is a clear
 
 All messages contain a payload, meta data and unique identifier. The payload of the message is the functional description of what the message means. The combination of the class name of this object and the data it carries, describe the application's meaning of the message. The metadata allows you to describe the context in which a message is being sent. You can, for example, store tracing information, to allow the origin or cause of messages to be tracked. You can also store information to describe the security context under which a command is being executed.
 
-Watch coding example on YouTube: [The Core API of Axon](https://youtu.be/vnCxjWZrrk0)
+[Axon Coding Tutorial #2: - The Core API](https://youtu.be/vnCxjWZrrk0)
 
 > **Note**
 >

implementing-domain-logic/command-handling/command-handling.md

@@ -4,3 +4,6 @@ In this chapter we will cover the process of handling and dispatching commands w
 Topics like Aggregate modelling, external command handlers, command dispatching and testing will be covered here.
 For a more in depth explanation of what a Command Model or Aggregate is we recommend reading the 
 [DDD and CQRS Patterns](../../introduction/architecture-overview/ddd-cqrs-patters.md) chapter.
+
+[Axon Coding Tutorial #3: - The Command Model](https://youtu.be/7oy4w5THFEU)
+

implementing-domain-logic/event-handling/event-handling.md

@@ -1,3 +1,5 @@
 # Event handling
 
 Event handlers are the components that act on incoming events. They typically execute logic based on decisions that have been made by the command model. Usually, this involves updating view models or forwarding updates to other components, such as third party integrations. In some cases event handlers will throw events themselves based on \(patterns of\) events that they received, or even send commands to trigger further changes.
+
+[Axon Coding Tutorial #4: - The Query Model](https://youtu.be/jS1vfc5EohM)

implementing-domain-logic/query-handling/query-handling.md

@@ -1,3 +1,5 @@
 # Query handling
 
-Query handling components act on incoming query messages. They typically read data from the view models created by the event listeners. Query handling components typically do not raise new events or send commands.
+Query handling components act on incoming query messages. They typically read data from the view models created by the event listeners. Query handling components typically do not raise new events or send commands.
+
+[Axon Coding Tutorial #4: - The Query Model](https://youtu.be/jS1vfc5EohM)

introduction/quick-start.md

@@ -16,5 +16,5 @@ This page shows you how to start building your own application using Axon platfo
 
  7. Explore the `README.md`
 
- 8. Watch coding example on YouTube: [The Structure of an Axon Application](https://youtu.be/tqn9p8Duy54)
+ 8. [Axon Coding Tutorial #1: - The Structure of an Axon Application](https://youtu.be/tqn9p8Duy54)