Skip to content

Ensure server is ready for production deployment #31

Open

Description

@AlexJuca

Goal

Track the work required to move FKVS from an experimental in-memory key-value store toward a production-ready service.

This is a meta issue. The concrete work should happen in focused issues and PRs linked below.

Production-readiness tracks

Correctness and safety

Durability and recovery

Security and exposure

Operations and observability

Testing and release confidence

Resource management and scale

Definition of done for a first production-ready milestone

  • FKVS has a clearly documented durability mode: volatile cache only, snapshotting, AOF, or both.
  • The server handles nonblocking reads and writes correctly under backpressure.
  • Malformed client input cannot crash, corrupt, or hang the process.
  • Default deployment is safe: localhost bind by default or explicit bind address, auth/TLS story documented, and connection/request limits available.
  • CI runs Debug and Release builds, sanitizer jobs, strict warning jobs, and protocol/parser fuzz smoke tests.
  • Real server/client integration tests cover TCP, Unix sockets, pipelining, disconnects, partial frames, and shutdown.
  • Operational docs exist for config, logs, metrics, health checks, systemd/container deployment, backup/restore, and capacity limits.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions