ShippedRedis
Give your application a fast place for frequently used data and supported background-work patterns. Connect the cache your workload needs.
Use the cache for the right data
Cache frequently requested results so your application can reuse them instead of repeating expensive work. Set expiration and invalidation rules that fit the data. Treat the cache as part of your application design: stale product information, an expired session, and a temporary computed result have different consequences and should not share assumptions by accident.
Check the needs of sessions and queues
Redis-backed sessions and queue libraries can require different commands, persistence, and eviction settings from a simple key-value cache. Choose a supported configuration for the library and workload you use. Review those requirements before connecting a queue or moving tiers, especially when losing a value would also mean losing work or signing out a user.
Size cache capacity independently
Adjust cache resources without increasing every other part of the application. A dedicated cache can be selected separately from the app server and database. Before a change, review memory needs, connection behavior, and any state that must survive the move; a disposable response cache can be rebuilt, while queue and session state may need preservation.
A little more detail
Questions about Redis?
Can I use every Redis command and library unchanged?
Compatibility depends on the selected service and workload. Check the supported command and library contract, particularly for scripts, streams, queues, and administrative commands, before choosing a resource tier.
Is cached data a replacement for a database backup?
No. Store authoritative records in a suitable durable database and back them up. When Redis holds important sessions or queued work, select persistence, eviction, and recovery behavior explicitly for that use.
Background workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workersPostgreSQL
Connect a managed PostgreSQL database to your Shipped application, with private access, backups, and capacity that grows independently from compute.
Explore PostgreSQLIndependent scaling
Scale application compute, PostgreSQL, cache, and storage independently on Shipped, with resource-specific changes and costs you can review.
Explore Independent scaling
Node.js
Run Node.js services on Shipped with databases, background workers, secrets, and deployment logs. Ship from your agent or GitHub.
Explore Node.jsFrom your workspace to the web