Event-Driven Essentials

Does this service publish and consume events safely? Naming, schemas, delivery, ordering and lag, checked against its design.

13 rules · 38% checked automatically

Check your service against it

Apply this checklist to a service described in MICROSERVICE.md™: 5 of its 13 rules are checked against the design automatically, and each failing rule points to where to fix it.

0 of 13 ticked · kept in this browser only

Events

Observability

  • Consumer lag is monitored

    The service measures how far behind its consumers are and alerts before the delay hurts users.

    HighChecked by hand