Government Event Bus: backbone межведомственной архитектуры

Зачем государству event-driven core

Каждое значимое государственное действие — event: birth, marriage, payment, document issued, regulatory action. Без event bus — каждая связь между systems point-to-point.

Bus делает events shared infrastructure: producer publishes, consumers subscribe.

Структурные элементы

Topics. civil.birth.registered, tax.payment.received, permit.issued, court.decision.published.

Schema registry с contracts.

Producer guarantees. At-least-once, idempotent IDs.

Consumer patterns. Each maintains offset.

Dead letter queue.

Observability — throughput, lag, error rates per topic.

Government-specific concerns

Sensitivity. Citizen events содержат PII — encryption mandatory, access tightly controlled.

Auditability. Каждое event traced.

Latency. Some flows real-time critical (emergency alerts), others batch acceptable.

Cross-agency governance. Owner per topic clear.

Regulator visibility — events affecting compliance must be auditable.

Где обычно ломается

Bus есть, contracts нет.

PII в clear text — security incident.

Topic owner отсутствует.

Schema changes без consumer acknowledgement.

Operating model

Owner — central digital agency или CDO office.

Standards и governance centrally enforced.

Per-topic stewardship distributed.

Связанное

• /architecture/government-orchestration-platform/ — orchestration
• /insights/government-cross-agency-debt/ — integration debt
• /architecture/government-master-data-management/ — MDM
• /architecture/government-consent-architecture/ — consent