First, ordered occasion streams. Every agent motion produces an occasion with a worldwide sequence quantity. Any agent can reconstruct the present system state by studying the occasion stream. This eliminates the necessity for brokers to question one another instantly, which is the place the latency was hiding in our system.
Second, context propagation. Each occasion carries a context envelope that features the originating consumer request, present session state and any constraints or deadlines. When an agent receives an occasion, it has the complete image with out making extra calls. In our earlier structure, brokers have been making three to 5 round-trip calls simply to assemble sufficient context to behave on a single request. Third, coordination primitives. The backbone supplies built-in help for widespread patterns: sequential handoffs between brokers, parallel fan-out with aggregation, conditional routing primarily based on confidence scores and precedence preemption when pressing requests arrive. These patterns would in any other case have to be applied independently by every agent pair, duplicating logic and introducing inconsistency.
from collections import defaultdict
import time
class EventSpine:
def __init__(self):
self.sequence = 0
self.subscribers = defaultdict(checklist)
def publish(self, event_type, payload, context):
self.sequence += 1
occasion = Event(
seq=self.sequence,
sort=event_type,
payload=payload,
context=context,
timestamp=time.time()
)
for handler in self.subscribers[event_type]:
handler(occasion)
return occasion
def subscribe(self, event_type, handler):
self.subscribers[event_type].append(handler)Sreenivasa Reddy Hulebeedu Reddy
three issues the Event Spine solves
Problem one: race situations between brokers. Without coordination, our scheduling agent would ebook conferences earlier than the inquiry agent had completed amassing necessities. Customers acquired calendar invites for appointments that have been lacking important particulars. The Event Spine solved this by implementing sequential processing for dependent operations. The scheduling agent subscribes to requirement-complete occasions and solely acts after receiving affirmation that the inquiry agent has gathered every little thing wanted.
