How redis-field-engineering/redis-streams-java-dist works
Project type and purpose
• This is a full-stack sample application ("bluesky-sentiment-analysis") built on top of the “redis-streams-java” library.
• Purpose: ingest posts from the Bluesky API (producer), stream them into Redis, process for sentiment (consumer), expose results via a Java Spring API, display in a React frontend, and provide metrics dashboards (Prometheus/Grafana).
File structure
• Top-level “samples/bluesky-sentiment-analysis” contains:
• producer/ – Java service using BskyClientEndpoint to fetch posts
• consumer/ – Java service that reads raw posts, applies sentiment via core library
• core/ – shared domain model (Post.java) used by producer, consumer, and API
• api/ – Spring Boot application exposing REST endpoints and persisting to Redis via redis-streams-java
• frontend/ – React app built with Tailwind/CSS served by nginx
• docker-compose.yml – orchestrates producer, consumer, api, redis, grafana, prometheus
• prometheus.yml, grafana/ – monitoring configuration
• terraform/ – infrastructure as code for AWS/GCP Redis clusters
README for additional insights
• The library breaks down into TopicManager, TopicProducer, ConsumerGroup – all backed by Redis Streams.
• The sample app uses TopicProducer to push messages, ConsumerGroup to read and classify sentiment, and TopicManager for consumer-group stats.