Phase 2: Backend in Go implementieren #323
Labels
No labels
good first issue
has-pr
help wanted
idea
priority
critical
priority
high
priority
low
priority
medium
status
blocked
status
in-progress
status
needs-review
status
ready
type
bug
type
docs
type
enhancement
type
feature
type
refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#324 Phase 3: Worker-Migration zu Go evaluieren
customable/claude-mem
#322 Phase 1: OpenAPI-Contract für Backend-API definieren
customable/claude-mem
Reference
customable/claude-mem#323
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ziel
Das Backend (packages/backend + packages/database) als Go-Service neu implementieren, basierend auf der OpenAPI-Spec aus Phase 1.
Voraussetzungen
Tech-Stack (Vorschlag)
chioderechosqlc+pgx/go-sqlite3gorilla/websocketodernhooyr/websocketnet/httpnativgolang.org/x/time/rateprometheus/client_golangslog(stdlib)envconfigodervipergooseodergolang-migrateAufgaben
1. Projekt-Setup
go mod init)cmd/,internal/,pkg/2. Database-Layer
sqlc-Queries für alle Repository-Methoden schreiben3. Core Services
4. Middleware
5. Migration & Testing
6. Deployment
Erwartete Verbesserungen
Risiken
Teil von
#321 Backend-Migration: Inkrementeller Wechsel von Node/TypeScript zu Go