Chapter 1. Introducing streaming data
Figure 1.1. A generic real-time system with consumers
Figure 1.2. A generic real-time system with no consumers
Figure 1.3. Real-time computation and consumption split apart
Figure 1.4. A first view of a streaming data system
Figure 1.5. The streaming data architectural blueprint
Figure 1.6. The architectural blueprint with security identified
Figure 1.7. Architectural blueprint with emphasis on the first tier
Chapter 2. Getting data from clients: data ingestion
Figure 2.1. Architectural blueprint with emphasis on the collection tier
Figure 2.2. Basic request/response pattern
Figure 2.3. Client making asynchronous request to the service
Figure 2.4. Service async request/response pattern
Figure 2.5. Receiving the response to the traffic conditions request with an on-board streaming system
Figure 2.6. Visitor browsing while data is collected and their propensity-to-buy score is updated
Figure 2.7. General data flow for the publish/subscribe message pattern
Figure 2.8. Current traffic publish/subscribe message pattern
Figure 2.9. Comparing the request/response patterns to the stream pattern
Figure 2.10. Vehicle and traffic service with a load balancer
Figure 2.11. buffering layerclient datafault tolerancedatafrom clientsfault tolerancefault toleranceSearch stream with direct connection to single collection node
Figure 2.12. Collection tier with buffering layer in place
Figure 2.13. Collection scenario with our data-loss potential identified