FAQ
What are the risks, challenges and disadvantages of Event-Driven Architecture?
Go back
An Event-Driven Architecture introduces new patterns and concepts such as asynchronous processing, eventual consistency, read models. This might introduce some technical challenges if you don’t have experience with those.
The handling of errors is more intricate, it’s important to make sure events are always produced, not in a separate transaction. Eventual consistency means less predictability for timing, but also better scalability and faster systems in general.
Storing event logs for a longer time is supported by most event hubs, which means a backup solution or an active-passive cluster setup needs to be set up.