How kimyuuum/simultaneous-viewing-limit-system works
This is a Spring Boot microservice system for enforcing simultaneous VOD-viewing limits. A client submits start, force-start, or stop requests to Push Service; new connections are checked by Check Service, which consults Redis and publishes a conflict result through Kafka. Push Service then notifies subscribed users over WebSocket and can dispatch forced-connect or stop updates asynchronously. The source excerpts establish the HTTP and service calls; Kafka topic delivery between services is documented only generally, so that cross-service dispatch is shown as unverified.
Main entry points: ConnectService.java Connection flow · CheckViewingService.java Limit decision · NotificationService.java User notifications · NotificationController.java Request API
Components 13
Push service
- Request API
push-service/src/main/java/com/skb/pushservice/controller/NotificationController.java - Connection flow
push-service/src/main/java/com/skb/pushservice/service/ConnectService.java - User notifications
push-service/src/main/java/com/skb/pushservice/service/NotificationService.java - Event listener
push-service/src/main/java/com/skb/pushservice/message/MessageListener.java
Viewing checks
- Connection endpoint
check-service/src/main/java/com/skb/checkservice/controller/ConnectController.java - Limit decision
check-service/src/main/java/com/skb/checkservice/service/CheckViewingService.java
Messaging
- Check event sender
check-service/src/main/java/com/skb/checkservice/message/MessageSender.java - Push event sender
push-service/src/main/java/com/skb/pushservice/message/MessageSender.java - Kafka cluster
Viewing state
- Watch-log access
check-service/src/main/java/com/skb/checkservice/service/RedisClusterService.java - Redis cluster
Other components
- OTT client
- WebSocket clients
Connections 14
- OTT client → Request API: submits request
README.md - Request API → Connection flow: routes requests
push-service/src/main/java/com/skb/pushservice/controller/NotificationController.java - Connection flow → Connection endpoint: checks via HTTP
push-service/src/main/java/com/skb/pushservice/service/ConnectService.java - Connection endpoint → Limit decision: delegates check
check-service/src/main/java/com/skb/checkservice/controller/ConnectController.java - Limit decision → Watch-log access: checks and updates
check-service/src/main/java/com/skb/checkservice/service/CheckViewingService.java - Watch-log access → Redis cluster: reads and writes
check-service/src/main/java/com/skb/checkservice/service/RedisClusterService.java - Limit decision → Check event sender: publishes conflict
check-service/src/main/java/com/skb/checkservice/service/CheckViewingService.java - Check event sender → Kafka cluster: sends event
check-service/src/main/java/com/skb/checkservice/message/MessageSender.java - Kafka cluster → Event listener: delivers event
- Event listener → User notifications: dispatches notification
push-service/src/main/java/com/skb/pushservice/message/MessageListener.java - Connection flow → User notifications: notifies users
push-service/src/main/java/com/skb/pushservice/service/ConnectService.java - User notifications → WebSocket clients: sends messages
push-service/src/main/java/com/skb/pushservice/service/NotificationService.java - Connection flow → Push event sender: sends force or stop
push-service/src/main/java/com/skb/pushservice/service/ConnectService.java - Push event sender → Kafka cluster: sends event