MVCC and TTL Support

[ankur-anand]

Each log manifestation currently performs in-place updates, overwriting existing values directly. This approach has limitations:

• No versioning support for concurrent transactions
• Cannot maintain historical versions for time-travel queries or auditing
• Lacks built-in support for automatic key expiration
• Potential for write conflicts in high-concurrency scenarios

Implement Multi-Version Concurrency Control (MVCC) with TTL-based expiry

• this will improve the concurrency of the txn system.
• Point-in-Time Queries
• Better CRDT system

But this will also have Storage overhead for maintaining multiple versions and will need Compaction strategy to merge/remove old versions

FIrst question is it worth it and what are uses cases if we need this ?

[ankur-anand]

optimistic txn conflict: Concurrency is handled using Tracking per-key commit LSNs and active txn begin LSNs to detect and reject stale txn commits across KV, row, and LOB writes.
#183

[bhati00]

Hi @ankur-anand ,

I'd like to start contributing to unisonndb, but I'm still a beginner with Go. For now, I'm looking for beginner friendly issues anything related to refactoring, maintenance, or smaller improvements within the existing codebase. As I get more comfortable, I can gradually take on more complex features. Please open some beginner-friendly issues that I can work on?

[ankur-anand]

Hi @bhati00 Thanks a lot for your interest in contributing to UnisonDB — really appreciate it!

Since you’re getting started with Go, I can definitely create some beginner-friendly issues focused on refactoring, cleanup, small improvements, and other low-complexity tasks. These should help you get familiar with the codebase without feeling overwhelmed.

I’ll open a set of good-first-issue items soon and tag you so you can pick whichever feels comfortable.

Excited to have you onboard — feel free to ask anything anytime!

[ankur-anand]

@bhati00 Check if you can pick something from this Issue: #185

[bhati00]

@bhati00 Check if you can pick something from this Issue: #185Sure, i'll start working on that.