Redis is one of the fastest in-memory data stores available today. It powers caching layers, message queues, session storage, analytics pipelines, and real-time event systems across thousands of companies. With Nodlyn's new Redis connector, these capabilities become first-class citizens inside your workflows — without sacrificing the local-first philosophy.
Why Redis Fits Perfectly in Local-First Automation
Redis is lightweight, embeddable, and extremely fast. Most deployments run on-prem, inside containers, or even on developer laptops. This makes it a natural match for Nodlyn's execution model: your workflows run locally, your data stays local, and your automation remains under your control.
Instead of sending keys, messages, or credentials to a cloud automation platform, Nodlyn connects directly to your Redis instance — whether it's running on localhost, a Docker container, or a private server.
The Redis Connector: What It Can Do
The connector exposes four core capabilities that cover the most common Redis workflows:
- GET — read a string value from a key
- SET — write a value with optional TTL
- DELETE — remove keys safely
- PUBLISH — send messages to Pub/Sub channels
Each capability is implemented as a standard Nodlyn node, with schema-driven settings and predictable outputs. No custom UI code, no special components — everything flows through the existing inspector and palette.
Connection Settings: Simple, Explicit, Secure
Every Redis node shares a unified connection schema:
- Host — usually
localhost - Port — default
6379 - Password — optional, stored securely
- Database — logical DB index (0–15)
- Use TLS — toggle for secure connections
This keeps configuration consistent across all Redis operations. Nodlyn encrypts secrets locally using AES‑256‑GCM, so your Redis password never leaves your machine.
Dry-Run Support: Safe by Default
Every Redis executor implements Nodlyn's dry-run mode. This means:
- No keys are written
- No messages are published
- No destructive operations occur
Dry-run lets you validate workflows, inspect outputs, and debug pipelines without touching your actual Redis data.
Real-Time Messaging with Redis Pub/Sub
Redis Pub/Sub is ideal for lightweight event-driven automation. With the PUBLISH capability, Nodlyn can broadcast messages to any channel:
events.orders
events.inventory
system.alertsDownstream nodes can react to these events, transform them, or forward them to other systems. A future update will introduce a Redis Subscribe Trigger, enabling workflows to start automatically when messages arrive.
Performance Characteristics
Because Redis is in-memory and Nodlyn executes locally, operations are extremely fast:
- GET and SET complete in microseconds
- DELETE is instant for single keys
- PUBLISH delivers messages with near-zero latency
There is no cloud round-trip, no external API gateway, and no vendor throttling. Your automation runs at the speed of your hardware.
Cloud-Compatible, But Still Local-First
All Redis capabilities are marked CloudCompatible. If you choose to run workflows in Nodlyn Cloud, Redis nodes will work exactly the same — connecting to your Redis instance over a secure channel.
But the philosophy remains unchanged: you decide where your data lives.
The Bottom Line
Redis brings high-performance data access and real-time messaging to Nodlyn workflows. Combined with Nodlyn's local-first execution model, you get a powerful automation stack that is fast, private, and fully under your control.
Whether you're caching API responses, managing session data, coordinating microservices, or broadcasting events, Redis fits seamlessly into the Nodlyn ecosystem.