⚡
  • HOME
  • NEWS
  • SERVICES
  • ARCHITECTURE
  • TECH STACK
  • PORTFOLIO
  • ABOUT
  • CONTACT
HOMENEWSSERVICESARCHITECTURETECH STACKPORTFOLIOABOUTCONTACT
© 2026 Miodrag Gromilić. All rights reserved.
HOMENEWSSERVICESTECH STACKPORTFOLIOCONTACTABOUTFAQs
Back to Skills

Redis

Since 2009In-memory data store for caching, sessions, queues, and pub/sub

In-memory data store for caching, sessions, queues, and pub/sub — in every production stack.

Overview

Every production app uses Redis — cache, sessions, job queues (Horizon), rate limiting, leaderboards, pub/sub, distributed locks. Proper eviction policies, RDB+AOF persistence, Sentinel for HA. Streams for event sourcing.

Use Cases

  • Caching
  • sessions
  • queues
  • rate limiting
  • pub/sub
  • leaderboards
  • distributed locks
  • feature flags

Advantages

  • Extremely fast
  • versatile data structures
  • pub/sub
  • built-in TTL
  • Sentinel HA
  • streams

Considerations

  • Size limited by RAM
  • persistence latency spikes
  • cluster complexity
  • license changes

Works Great With

LaravelNode.jsDockerPostgreSQLNginxKubernetes

Related Technologies

PostgreSQL
Since 1996
MySQL
Since 1995
SQLite
Since 2000
MongoDB
Since 2009
Elasticsearch
Since 2010
Pinecone
Since 2019
Back to Skills CONTACT