Claude Code for Upstash: Serverless Redis and Kafka — Claude Skills 360 Blog
Blog / AI / Claude Code for Upstash: Serverless Redis and Kafka
AI

Claude Code for Upstash: Serverless Redis and Kafka

Published: July 13, 2027
Read time: 6 min read
By: Claude Skills 360

Upstash provides serverless Redis and Kafka with HTTP-based SDKs that work at the edge — Redis.fromEnv() auto-reads UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN. await redis.set("key", value, { ex: 60 }) stores with TTL. await redis.get("key") retrieves. await redis.hset("hash", { field: value }) and redis.hgetall("hash") for hash maps. Rate limiting: new Ratelimit({ redis, limiter: Ratelimit.slidingWindow(10, "10 s") }) and const { success, limit, remaining } = await ratelimit.limit(identifier). QStash message queue: const client = new Client({ token }), client.publishJSON({ url: webhookUrl, body: payload, delay: 60 }) schedules delivery. client.schedules.create({ cron: "0 9 * * *", destination: url, body: {} }) creates recurring jobs. Kafka: const kafka = new Kafka({ url, username, password }), const producer = kafka.producer(), await producer.produce("topic", { value: JSON.stringify(event) }), kafka.consumer({ groupId }).consume({ instanceId, topics, autoOffsetReset: "latest" }, handler). Pipeline: const p = redis.pipeline(); p.set("a", 1); p.incr("counter"); await p.exec(). Claude Code generates Upstash Redis caching, serverless rate limiting, and QStash background job queues.

CLAUDE.md for Upstash

## Upstash Stack
- Version: @upstash/redis >= 1.34, @upstash/ratelimit >= 2.x, @upstash/qstash >= 2.x
- Redis init: const redis = Redis.fromEnv() — needs UPSTASH_REDIS_REST_URL + UPSTASH_REDIS_REST_TOKEN
- Get/set: await redis.set("key", value, { ex: 300 }); const val = await redis.get<MyType>("key")
- Hash: await redis.hset("user:123", { name, email }); const user = await redis.hgetall("user:123")
- Rate limit: const rl = new Ratelimit({ redis, limiter: Ratelimit.slidingWindow(100, "60 s"), prefix: "@app" })
- Rate check: const { success, remaining, reset } = await rl.limit(userId)
- QStash publish: await qstash.publishJSON({ url: WEBHOOK, body: job, retries: 3 })
- All ops are HTTP, work in Vercel Edge Functions / Cloudflare Workers / Node.js

Upstash Redis Client

// lib/upstash/redis.ts — Upstash Redis helpers with type safety
import { Redis } from "@upstash/redis"

// Auto-reads UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN
export const redis = Redis.fromEnv()

/** Cache wrapper — get or fetch and cache */
export async function cached<T>(
  key: string,
  fetcher: () => Promise<T>,
  ttlSeconds = 300,
): Promise<T> {
  const cached = await redis.get<T>(key)
  if (cached !== null) return cached

  const value = await fetcher()
  await redis.set(key, value, { ex: ttlSeconds })
  return value
}

/** Invalidate cache by key or prefix pattern */
export async function invalidate(pattern: string): Promise<number> {
  if (!pattern.includes("*")) {
    return redis.del(pattern)
  }
  // Scan and delete matching keys
  let cursor = 0
  let deleted = 0
  do {
    const [nextCursor, keys] = await redis.scan(cursor, { match: pattern, count: 100 })
    cursor = Number(nextCursor)
    if (keys.length > 0) {
      await redis.del(...keys)
      deleted += keys.length
    }
  } while (cursor !== 0)
  return deleted
}

// ── Session store ─────────────────────────────────────────────────────────

export type SessionData = {
  userId: string
  email: string
  role: string
  expiresAt: number
}

export async function setSession(sessionId: string, data: SessionData, ttlSeconds = 86400): Promise<void> {
  await redis.hset(`session:${sessionId}`, data)
  await redis.expire(`session:${sessionId}`, ttlSeconds)
}

export async function getSession(sessionId: string): Promise<SessionData | null> {
  const data = await redis.hgetall<SessionData>(`session:${sessionId}`)
  if (!data) return null
  if (Date.now() > data.expiresAt) {
    await redis.del(`session:${sessionId}`)
    return null
  }
  return data
}

export async function deleteSession(sessionId: string): Promise<void> {
  await redis.del(`session:${sessionId}`)
}

// ── Leaderboard (sorted set) ──────────────────────────────────────────────

export async function addScore(board: string, userId: string, score: number): Promise<void> {
  await redis.zadd(board, { score, member: userId })
}

export async function getLeaderboard(
  board: string,
  limit = 10,
): Promise<Array<{ userId: string; score: number; rank: number }>> {
  const results = await redis.zrange(board, 0, limit - 1, {
    rev: true,
    withScores: true,
  })

  const entries: Array<{ userId: string; score: number; rank: number }> = []
  for (let i = 0; i < results.length; i += 2) {
    entries.push({
      userId: results[i] as string,
      score: Number(results[i + 1]),
      rank: i / 2 + 1,
    })
  }
  return entries
}

export async function getUserRank(
  board: string,
  userId: string,
): Promise<{ rank: number; score: number } | null> {
  const [rank, score] = await Promise.all([
    redis.zrevrank(board, userId),
    redis.zscore(board, userId),
  ])
  if (rank === null || score === null) return null
  return { rank: rank + 1, score: Number(score) }
}

// ── Atomic pipeline ───────────────────────────────────────────────────────

/** Increment a counter and get current value atomically */
export async function incrementCounter(
  key: string,
  ttlSeconds?: number,
): Promise<number> {
  const p = redis.pipeline()
  p.incr(key)
  if (ttlSeconds) p.expire(key, ttlSeconds)
  const results = await p.exec()
  return results[0] as number
}

Rate Limiting Middleware

// lib/upstash/ratelimit.ts — serverless rate limiting with Upstash
import { Ratelimit } from "@upstash/ratelimit"
import { Redis } from "@upstash/redis"

const redis = Redis.fromEnv()

// Pre-built limiters for different use cases
export const limiters = {
  // API endpoint: 100 req/min per user
  api: new Ratelimit({
    redis,
    limiter: Ratelimit.slidingWindow(100, "60 s"),
    prefix: "@api",
    analytics: true, // Records to Upstash console
  }),

  // Auth endpoints: 5 attempts per 15 min per IP (stricter)
  auth: new Ratelimit({
    redis,
    limiter: Ratelimit.fixedWindow(5, "15 m"),
    prefix: "@auth",
  }),

  // AI generation: 10 req/hour per user
  ai: new Ratelimit({
    redis,
    limiter: Ratelimit.tokenBucket(10, "1 h", 10),
    prefix: "@ai",
  }),
}

export type RateLimitResult = {
  success: boolean
  limit: number
  remaining: number
  reset: number // Unix timestamp in ms
  retryAfter?: number // seconds to wait
}

export async function checkRateLimit(
  limiterName: keyof typeof limiters,
  identifier: string,
): Promise<RateLimitResult> {
  const { success, limit, remaining, reset } = await limiters[limiterName].limit(identifier)

  return {
    success,
    limit,
    remaining,
    reset,
    retryAfter: success ? undefined : Math.ceil((reset - Date.now()) / 1000),
  }
}

// Next.js middleware usage:
// import { NextResponse } from "next/server"
// export async function middleware(req: NextRequest) {
//   const ip = req.ip ?? req.headers.get("x-forwarded-for") ?? "anonymous"
//   const { success, retryAfter } = await checkRateLimit("api", ip)
//   if (!success) {
//     return NextResponse.json({ error: "Rate limit exceeded" }, {
//       status: 429,
//       headers: { "Retry-After": String(retryAfter) },
//     })
//   }
//   return NextResponse.next()
// }

QStash Background Jobs

// lib/upstash/qstash.ts — durable background job queue with QStash
import { Client as QStashClient, Receiver } from "@upstash/qstash"

export const qstash = new QStashClient({
  token: process.env.QSTASH_TOKEN!,
})

const WEBHOOK_BASE = process.env.NEXT_PUBLIC_APP_URL!

// ── Publish jobs ───────────────────────────────────────────────────────────

export async function enqueueEmail(payload: {
  to: string
  subject: string
  template: string
  data: Record<string, unknown>
}): Promise<string> {
  const { messageId } = await qstash.publishJSON({
    url: `${WEBHOOK_BASE}/api/jobs/email`,
    body: payload,
    retries: 3,
    delay: 0,
  })
  return messageId
}

export async function scheduleReport(
  reportType: string,
  userId: string,
  delaySeconds = 0,
): Promise<string> {
  const { messageId } = await qstash.publishJSON({
    url: `${WEBHOOK_BASE}/api/jobs/report`,
    body: { reportType, userId },
    retries: 2,
    ...(delaySeconds > 0 ? { delay: delaySeconds } : {}),
  })
  return messageId
}

export async function createRecurringJob(
  name: string,
  endpoint: string,
  cron: string,
  body?: Record<string, unknown>,
): Promise<string> {
  const schedule = await qstash.schedules.create({
    cron,
    destination: `${WEBHOOK_BASE}${endpoint}`,
    body: body ? JSON.stringify(body) : undefined,
    headers: body ? { "Content-Type": "application/json" } : undefined,
  })
  return schedule.scheduleId
}

// ── Verify incoming QStash requests ──────────────────────────────────────

export const receiver = new Receiver({
  currentSigningKey: process.env.QSTASH_CURRENT_SIGNING_KEY!,
  nextSigningKey: process.env.QSTASH_NEXT_SIGNING_KEY!,
})

export async function verifyQStashRequest(req: Request): Promise<boolean> {
  const signature = req.headers.get("upstash-signature")
  if (!signature) return false

  const body = await req.text()
  try {
    await receiver.verify({ signature, body })
    return true
  } catch {
    return false
  }
}

// app/api/jobs/email/route.ts usage:
// export async function POST(req: Request) {
//   if (!await verifyQStashRequest(req)) return new Response("Unauthorized", { status: 401 })
//   const { to, subject, template, data } = await req.json()
//   await sendEmail({ to, subject, template, data })
//   return new Response("OK")
// }

For the Redis Cloud (Redis Inc.) alternative when needing a traditional persistent Redis instance with full Redis module support (RedisSearch, RedisJSON, RedisGraph, RedisTimeSeries) and sub-millisecond latency from a long-running server — Redis Cloud is a fully managed persistent Redis while Upstash’s serverless HTTP model is uniquely suited for edge runtimes and functions that can’t hold TCP connections, see the Redis guide. For the Vercel KV alternative when already deploying on Vercel and wanting a Redis-backed store with zero additional configuration through the Vercel dashboard — Vercel KV is powered by Upstash under the hood with slightly fewer features exposed, so Upstash directly gives you more control (QStash, Kafka, analytics) at the same underlying service, see the Vercel KV guide. The Claude Skills 360 bundle includes Upstash skill sets covering Redis caching, rate limiting, and QStash job queues. Start with the free tier to try serverless Redis generation.

Keep Reading

AI

Claude Code for email.contentmanager: Python Email Content Accessors

Read and write EmailMessage body content with Python's email.contentmanager module and Claude Code — email contentmanager ContentManager for the class that maps content types to get and set handler functions allowing EmailMessage to support get_content and set_content with type-specific behaviour, email contentmanager raw_data_manager for the ContentManager instance that handles raw bytes and str payloads without any conversion, email contentmanager content_manager for the standard ContentManager instance used by email.policy.default that intelligently handles text plain text html multipart and binary content types, email contentmanager get_content_text for the handler that returns the decoded text payload of a text-star message part as a str, email contentmanager get_content_binary for the handler that returns the raw decoded bytes payload of a non-text message part, email contentmanager get_data_manager for the get-handler lookup used by EmailMessage get_content to find the right reader function for the content type, email contentmanager set_content text for the handler that creates and sets a text part correctly choosing charset and transfer encoding, email contentmanager set_content bytes for the handler that creates and sets a binary part with base64 encoding and optional filename Content-Disposition, email contentmanager EmailMessage get_content for the method that reads the message body using the registered content manager handlers, email contentmanager EmailMessage set_content for the method that sets the message body and MIME headers in one call, email contentmanager EmailMessage make_alternative make_mixed make_related for the methods that convert a simple message into a multipart container, email contentmanager EmailMessage add_attachment for the method that attaches a file or bytes to a multipart message, and email contentmanager integration with email.message and email.policy and email.mime and io for building high-level email readers attachment extractors text body accessors HTML readers and policy-aware MIME construction pipelines.

5 min read Feb 12, 2029
AI

Claude Code for email.charset: Python Email Charset Encoding

Control header and body encoding for international email with Python's email.charset module and Claude Code — email charset Charset for the class that wraps a character set name with the encoding rules for header encoding and body encoding describing how to encode text for that charset in email messages, email charset Charset header_encoding for the attribute specifying whether headers using this charset should use QP quoted-printable encoding BASE64 encoding or no encoding, email charset Charset body_encoding for the attribute specifying the Content-Transfer-Encoding to use for message bodies in this charset such as QP or BASE64, email charset Charset output_codec for the attribute giving the Python codec name used to encode the string to bytes for the wire format, email charset Charset input_codec for the attribute giving the Python codec name used to decode incoming bytes to str, email charset Charset get_output_charset for returning the output charset name, email charset Charset header_encode for encoding a header string using the charset's header_encoding method, email charset Charset body_encode for encoding body content using the charset's body_encoding, email charset Charset convert for converting a string from the input_codec to the output_codec, email charset add_charset for registering a new charset with custom encoding rules in the global charset registry, email charset add_alias for adding an alias name that maps to an existing registered charset, email charset add_codec for registering a codec name mapping for use by the charset machinery, and email charset integration with email.message and email.mime and email.policy and email.encoders for building international email senders non-ASCII header encoders Content-Transfer-Encoding selectors charset-aware message constructors and MIME encoding pipelines.

5 min read Feb 11, 2029
AI

Claude Code for email.utils: Python Email Address and Header Utilities

Parse and format RFC 2822 email addresses and dates with Python's email.utils module and Claude Code — email utils parseaddr for splitting a display-name plus angle-bracket address string into a realname and email address tuple, email utils formataddr for combining a realname and address string into a properly quoted RFC 2822 address with angle brackets, email utils getaddresses for parsing a list of raw address header strings each potentially containing multiple comma-separated addresses into a list of realname address tuples, email utils parsedate for parsing an RFC 2822 date string into a nine-tuple compatible with time.mktime, email utils parsedate_tz for parsing an RFC 2822 date string into a ten-tuple that includes the UTC offset timezone in seconds, email utils parsedate_to_datetime for parsing an RFC 2822 date string into an aware datetime object with timezone, email utils formatdate for formatting a POSIX timestamp or the current time as an RFC 2822 date string with optional usegmt and localtime flags, email utils format_datetime for formatting a datetime object as an RFC 2822 date string, email utils make_msgid for generating a globally unique Message-ID string with optional idstring and domain components, email utils decode_rfc2231 for decoding an RFC 2231 encoded parameter value into a tuple of charset language and value, email utils encode_rfc2231 for encoding a string as an RFC 2231 encoded parameter value, email utils collapse_rfc2231_value for collapsing a decoded RFC 2231 tuple to a Unicode string, and email utils integration with email.message and email.headerregistry and datetime and time for building address parsers date formatters message-id generators header extractors and RFC-compliant email construction utilities.

5 min read Feb 10, 2029

Put these ideas into practice

Claude Skills 360 gives you production-ready skills for everything in this article — and 2,350+ more. Start free or go all-in.

Back to Blog

Get 360 skills free