Stream Fundamentals.
Data streams are continuous flows of events. Understanding stream types and protocols is the foundation for connecting your application to ABIS behavioral analysis.
Event streams represent a fundamental shift from request-response patterns. Instead of polling for changes, streams push data continuously as events occur. For behavioral analysis, this means capturing user actions in real-time rather than processing logs after the fact.
ABIS integration supports multiple streaming protocols: WebSockets for bidirectional communication, Server-Sent Events (SSE) for server-to-client push, and HTTP long polling as a fallback. Protocol selection depends on your infrastructure, latency requirements, and browser support constraints.
The key advantage of streaming over batch processing is temporal context. When ABIS receives events as they happen, it can detect anomalies in real-time—a sudden burst of activity, unusual navigation patterns, or behavioral deviations that batch processing would only catch hours later.
WEBSOCKET STREAMS
Full-duplex, persistent connection. Lowest latency, bidirectional communication. Ideal for real-time applications requiring immediate ABIS feedback.
LATENCY: <50msSERVER-SENT EVENTS
Server-to-client push over HTTP. Simpler than WebSockets, automatic reconnection. Perfect for one-way behavioral event streaming.
LATENCY: 50-100msHTTP LONG POLLING
Fallback protocol for restricted environments. Client holds connection open until server has data. Higher overhead but universal compatibility.
LATENCY: 100-500msBATCH UPLOAD
Periodic bulk uploads of collected events. Highest latency but lowest connection overhead. Use for non-critical behavioral signals.
LATENCY: 1-60s