<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Evently – App Flow</title><link>/docs/app-flow/</link><description>Recent content in App Flow on Evently</description><generator>Hugo -- gohugo.io</generator><atom:link href="/docs/app-flow/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs: Events Manager</title><link>/docs/app-flow/events_manager/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/app-flow/events_manager/</guid><description>
&lt;p>The Events Manager is a crucial component of the application and holds control over events and users. It consists of two main layers: the domain layer and the infrastructure layer.&lt;/p>
&lt;h2 id="domain-layer">Domain Layer&lt;/h2>
&lt;p>This layer handles the business logic. It manages events and users. Additionally, it emits events when specific actions occur, such as when an event is created, updated, or deleted. When a user registers for an event, an event is emitted as well.
You can check &lt;a href="https://github.com/julian776/evently/tree/main/events-manager/domain/events/usecases">use cases&lt;/a> to make a better idea.&lt;/p>
&lt;h2 id="infrastructure-layer">Infrastructure Layer&lt;/h2>
&lt;p>This layer deals with the implementation details of the Events Manager.&lt;/p></description></item><item><title>Docs: Front</title><link>/docs/app-flow/front/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/app-flow/front/</guid><description>
&lt;p>The Frontend is developed using Angular and tries to implement the same structure as is proposed.&lt;/p></description></item><item><title>Docs: Notifier</title><link>/docs/app-flow/notifier/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/app-flow/notifier/</guid><description>
&lt;p>The Notifier acts as a receiver for messages sent by the Events Manager. It registers handlers for specific types of messages and listens to specific queues within a message broker. When a message arrives, the Notifier executes the appropriate handler for that particular type of message. This allows the Notifier to perform actions based on the events received from the Events Manager, such as sending notifications to users.&lt;/p>
&lt;h2 id="domain-layer">Domain Layer&lt;/h2>
&lt;p>This layer handles the business logic.&lt;/p>
&lt;p>You can check &lt;a href="https://github.com/julian776/evently/tree/main/notifier/domain/events/usecases">use cases&lt;/a> to make a better idea.&lt;/p>
&lt;h2 id="infrastructure-layer">Infrastructure Layer&lt;/h2>
&lt;p>This layer deals with the implementation details of the Events Manager.&lt;/p>
&lt;p>The most interesting is the &lt;a href="https://github.com/julian776/evently/blob/main/notifier/infrastructure/rabbit/listener.go">listener&lt;/a>.&lt;/p></description></item></channel></rss>