Polling advantages
Simple to implement, works with any REST API, easy to cache, survives connection drops. Poll every 10–30s with server-side proxy for most cricket apps.
WebSocket advantages
Lower latency for push updates, efficient for many subscribers to the same match. Requires your own pub/sub layer since most cricket APIs are REST-only.
Recommendation
Start with polled REST + Redis cache. Add WebSockets on your backend only when you need sub-second push to thousands of concurrent users per match.