Event-Driven Architecture
Event-driven, architecture, mein, services, EVENTS, (jaise, "OrderPlaced", "PaymentProcessed") ko, PUBLISH, karti, hain, aur, DUSRI, services, INKO, SUBSCRIBE, karके, REACT, karti, HAIN — services, EK, DUSRE, ko, DIRECTLY, CALL, NAHI, karte.
Ye, PATTERN, HIGH, DECOUPLING, deta hai — NAYI, services, ADD, ki, ja, sakti, HAIN, JO, EXISTING, EVENTS, ko, SUBSCRIBE, karti, hain, bina, PUBLISHER, service, ke, code, ko, TOUCH, kiye.
// Order service, EVENT, publish, karta, hai:
eventBus.publish("OrderPlaced", { orderId, userId, items });
// MULTIPLE, services, INDEPENDENTLY, react, karti, hain:
// - inventory-service: stock, kam, karta, hai
// - notification-service: email, bhejta, hai
// - analytics-service: metrics, update, karta, hai- Event-driven = services, events, publish/subscribe, karte, hain, directly, call, karne, ke, BAJAYE
- High decoupling — naye, subscribers, add, ho, sakte, hain, bina, publisher, touch, kiye
- Debugging, harder, hoti, hai — distributed, tracing, ZAROORI, ho, jaata, hai
Events, ke, SCHEMA, ko, TIME, ke, saath, EVOLVE, karna, PADТA, hai — BACKWARD-COMPATIBLE, changes, (jaise, naye, OPTIONAL, fields) SAFE, HAIN — SCHEMA, REGISTRY, tools, (jaise, Confluent, Schema, Registry) COMPATIBILITY, ko, ENFORCE, karne, mein, HELP, karte, hain.
"Event, notification" mein, EVENT, sirf, EK, MINIMAL, SIGNAL, hai (jaise, "OrderChanged, id=123") aur, subscribers, ko, FULL, DETAILS, ke, liye, SEPARATELY, FETCH, karna, PADТA, hai. "Event-carried, state, transfer" mein, event, mein, hi, SAARA, RELEVANT, data, INCLUDED, hota hai.