Upstash

<Note>You can use any Redis® client, but we recommend @upstash/redis</Note>

<Note type="info">
  You can use any Redis® client, but we recommend @upstash/redis
</Note>

<Note type="tip">
  You can use any Redis® client, but we recommend @upstash/redis
</Note>

<Note type="caution">
  You can use any Redis® client, but we recommend @upstash/redis
</Note>

<Note type="danger">
  You can use any Redis® client, but we recommend @upstash/redis
</Note>

<Note title="custom">
  You can use any Redis® client, but we recommend @upstash/redis
</Note>
<Note title="custom" danger>
  You can use any Redis® client, but we recommend @upstash/redis
</Note>

```javascript title:"pages/api/hello.ts"
import type { NextRequest } from 'next/server';
import { Redis } from '@upstash/redis';
```

```javascript:pages/api/hello.ts showLineNumbers {5-8,12}
import type { NextRequest } from 'next/server';
import { Redis } from '@upstash/redis'
```

Tags group posts under /blog/tag/<tag>. Conventions:

• Always use lowercase kebab-case in frontmatter: aws-lambda, not AWS Lambda or awslambda. Don't wrap tags in quotes.
• Tag matching is case- and whitespace-insensitive (via normalizeTag in src/utils/tags.ts), so Vector, vector, semantic search and semantic-search resolve to the same page — but please write the normalized form so counts and the popular-tag row dedupe correctly.
• Add every topic that applies. An article about Upstash Redis Search should include both redis and search, so it surfaces under /blog/tag/redis and /blog/tag/search. Posts that are about semantic search must carry both search and semantic-search.
• Display labels for multi-word or acronym tags live in TAG_NAMES (src/utils/const.ts). If you introduce a new multi-word tag, add an entry so the pill row renders it nicely (e.g. "feature-flags": "Feature Flags"). Single-word tags fall back to CSS capitalize.

---
title: "A First Look at Upstash Redis Search"
slug: first-look-at-upstash-redis-search
authors: [josh]
tags: [redis, search]
---

Canonical tag names (use these; don't invent variants):

If you ever need to re-run the consolidation (e.g. after importing external posts), scripts/consolidate-blog-tags.mjs is idempotent — it rewrites tags: [...] in every data/blog/*.mdx according to the rules above.