Event Driven Architecture
<hr>
Event-driven architecture (EDA) is a software design pattern that enables an organization to detect “events” or important business moments
<hr>
What’s the difference between a FIFO and a standard queue ❓ 📁
Standard queues guarantee that a message is delivered at least once and duplicates can be introduced into the queue. FIFO queues ensure a message is delivered exactly once and remains available until a consumer processes and deletes it; duplicates are not introduced into the queue.
How can the server be assured a message was properly received ❓
by recieving a response, else will throw an error.
What classic design pattern is best represented by event driven programming ❓ 📁
Event Notification , It is the most basic pattern describing event-centric communication facilitated by the Event Store.
How do you test an event driven system ❓ 📁
Unit Tests are the most basic tests you will write Your unit test will interact with this class directly, passing various Order values to it, and verifying the tax has been calculated properly.
Service Tests These tests verify the contract of services, that is given certain inputs, the service produces a certain output.
- Events have two primary functions:
- They are triggers of side effects somewhere in the system.
- They are also carriers of arbitrary data.
<hr>
SNS
- simple notification services.
- publisher/subsicriber system.
- publish a message about some topic, then will be delivered to many subsicribers with diffrent types.
SQS
- simple queue service.
- queueing service for message processing.
- the system must poll the queue to discover a new event.
- processing in the queue will be for single consumer.
How To: Use SNS and SQS to Distribute and Throttle Events
<hr>