Occasion-driven architectures like this are a comparatively frequent design sample in distributed methods. Like different distributed growth fashions, they’ve their very own issues, particularly at scale. Whenever you’re getting tens or tons of of occasions a minute, it’s straightforward to detect and reply to the messages you’re searching for. However when your software or service grows to a number of hundred hundreds and even thousands and thousands of messages throughout a worldwide platform, what labored for a smaller system is prone to collapse underneath this new load.
At scale, event-driven methods change into complicated. Messages and occasions are delivered in many alternative varieties and saved in impartial silos, making them exhausting to extract and course of and sometimes requiring complicated question mechanisms. On the similar time, message queuing methods change into sluggish and congested, including latency and even letting messages day out. When you want to reply to occasions rapidly, this fragile state of affairs turns into exhausting to make use of and handle.
That’s the place Drasi is available in. It offers a greater strategy to automate the method of detecting and responding to related occasions, an strategy Microsoft describes as “the automation of clever reactions.” It’s supposed to be a light-weight device that doesn’t want a fancy, centralized retailer for occasion information, as a substitute benefiting from decentralization to search for occasions near the place they’re sourced, in log information and alter feeds.
