Supabase vs Neon 对比

// Supabase — RLS 保护的查询 + Storage 上传（TypeScript）
import { createClient } from '@supabase/supabase-js'

const supabase = createClient(
  process.env.SUPABASE_URL!,
  process.env.SUPABASE_ANON_KEY!
)

// 由 RLS 策略 "select_own_posts" 保护的表
const { data: posts, error } = await supabase
  .from('posts')
  .select('id, title, created_at')
  .eq('author_id', userId)
  .order('created_at', { ascending: false })
  .limit(20)

if (error) throw error

// 同一项目内的 Storage —— 带签名的上传 URL
const { data: uploadUrl } = await supabase.storage
  .from('avatars')
  .createSignedUploadUrl(`${userId}/profile.png`)

// Realtime —— 通过 Postgres Changes 实现实时监听
supabase
  .channel('posts-changes')
  .on(
    'postgres_changes',
    { event: 'INSERT', schema: 'public', table: 'posts' },
    (payload) => console.log('新帖子:', payload.new)
  )
  .subscribe()

# Neon — CLI + serverless driver（bash + TypeScript）

# --- bash：每个 PR 打开/删除一个分支（CI 步骤）---
# 1）从主分支创建即时 copy-on-write 克隆
neon branches create \
  --project-id $NEON_PROJECT_ID \
  --name "preview/pr-${PR_NUMBER}" \
  --parent main

# 2）获取该分支的 pooled 连接字符串
neon connection-string "preview/pr-${PR_NUMBER}" --pooled

# 3）PR 关闭后删除分支（保持预览环境整洁）
neon branches delete "preview/pr-${PR_NUMBER}" --project-id $NEON_PROJECT_ID

// --- TypeScript：在无服务器环境（Vercel Edge/Cloudflare Workers）中使用基于 HTTP 的驱动 ---
import { neon } from '@neondatabase/serverless'

const sql = neon(process.env.DATABASE_URL!) // pooled，位于 PgBouncer 之后

const rows = await sql`
  SELECT id, title, created_at
  FROM posts
  WHERE author_id = ${userId}
  ORDER BY created_at DESC
  LIMIT 20
`