devloperdevesh / devloperdevesh/FaultPlane

feat(storage): introduce checkpoint ring buffer storage experiment

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
2
Forks
1
Avg merge
14m
Merged PRs (30d)
57

Description

Overview

The current memory storage implementation uses Go synchronization primitives to protect workflow state.

This issue explores alternative storage layouts optimized for high-frequency checkpoint operations.

Proposed Work

Implement an experimental ring buffer based storage component:

  • Create a fixed-size checkpoint buffer
  • Manage read/write positions safely
  • Evaluate atomic operations using sync/atomic
  • Add benchmarks comparing current storage and ring buffer implementation

Expected Outcome

Provide benchmark results for:

  • Write throughput
  • Read performance
  • Memory allocation behavior
  • Concurrent access patterns

Requirements

  • Existing storage interfaces must remain compatible
  • Current MemoryStore behavior should continue working
  • New implementation should be isolated and testable

Notes

This is a performance exploration. The default storage backend should remain unchanged until benchmarks justify adoption.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing MemoryStore implementation and storage interfaces, then review how checkpoint reads and writes are synchronized. Design the isolated fixed-size ring buffer around compatible interfaces and safe read/write positions. Add tests and benchmarks covering throughput, reads, allocations, and concurrent access, while confirming the current MemoryStore behavior remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.