Services behind the platform.
WHAT THE BACKEND PROVIDES
Business logic beyond device management Customer accounts and permissions Rules and alerting Reporting Integration with other systems
WHAT TO SEPARATE
Device ingestion from business processing.
WHY
They scale differently and fail differently.
WHAT TO USE BETWEEN THEM
A queue.
WHAT MULTI-TENANCY REQUIRES
Devices, data and users scoped to a customer Authorisation checked on every access No possibility of crossing between customers
WHY THAT MATTERS ABSOLUTELY
Customers seeing each other's device data is a serious breach.
WHAT TO ENFORCE
Scoping at the data layer, not only in the interface.
WHAT ALERTING REQUIRES
Rules per customer Delivery by their chosen channel Records of what was sent Handling of delivery failure
WHAT TO AVOID
Alert rules evaluated by scanning all data Notifications sent without record Rules that cannot be tested
WHAT TO PROVIDE
A way for customers to test a rule.
WHAT TO MONITOR
Rule evaluation latency Notification delivery success Processing lag behind ingestion
