Deployment
This guide covers deploying Korvet in production environments.
Docker Deployment
Kubernetes Deployment
Deployment Manifest
apiVersion: apps/v1
kind: Deployment
metadata:
name: korvet
spec:
replicas: 3
selector:
matchLabels:
app: korvet
template:
metadata:
labels:
app: korvet
spec:
containers:
- name: korvet
image: redisfield/korvet:latest
ports:
- containerPort: 9092
env:
- name: KORVET_REDIS_HOST
value: redis-service
- name: KORVET_REDIS_PORT
value: "6379"
resources:
requests:
memory: "512Mi"
cpu: "500m"
limits:
memory: "2Gi"
cpu: "2000m"
livenessProbe:
httpGet:
path: /actuator/health/liveness
port: 8080
initialDelaySeconds: 30
periodSeconds: 10
readinessProbe:
httpGet:
path: /actuator/health/readiness
port: 8080
initialDelaySeconds: 10
periodSeconds: 5
High Availability
For production deployments:
-
Multiple instances: Run 3+ Korvet instances behind a load balancer
-
Redis cluster: Use Redis Cluster or Redis Enterprise for HA
-
Health checks: Configure liveness and readiness probes
-
Graceful shutdown: Allow time for in-flight requests to complete
Scaling
Korvet can be scaled horizontally:
-
Stateless: Each instance is independent
-
Load balancing: Use any TCP load balancer
-
Partition assignment: Clients connect to any instance