DEV Community

Discussion on: Syncing the Real Market: Consuming Brapi and Feeding Redis with Spring Boot

Collapse
 
buildbasekit profile image
buildbasekit

Clean and focused design.

  • Strong separation with a dedicated market data producer
  • Redis + TTL is the right call. Fail > stale data
  • Timezone handling is a great catch
  • Good resilience with per-ticker isolation

One thing to watch:

  • Fixed 30-min polling won’t scale long term

Looking forward to how the matching engine uses Redis as source of truth.

Collapse
 
rvneto profile image
Roberto de Vargas Neto • Edited

Great catch! The 30-minute interval is just a temporary constraint to stay within the Brapi free tier limits during development. I'm already planning to optimize this once the core architecture is fully stabilized. Glad you liked the Redis + TTL approach!

Collapse
 
buildbasekit profile image
buildbasekit

Makes sense, good call keeping it simple while stabilizing the core.

Once you move past free tier limits, event-driven or streaming-based updates could be interesting to explore instead of polling.

Curious to see how you evolve that part πŸ‘