Advanced C++ projects: concurrency, memory and systems programming
Advanced C++ projects that mirror real systems work: a thread pool, a lock-based message queue, a memory pool, a crash-safe key-value store, an order book and a linear-time regex engine.
Advanced C++ is less about syntax and more about guarantees. A message queue must never lose a message. A storage engine must survive a power cut mid-write. A regex engine must not hang on a hostile pattern. These projects ask you to make, and test, promises like those.
They form Devventura's Summit level. They assume you're comfortable with the standard library, templates and the material from the intermediate projects.
What you'll practise
- Concurrency: threads, mutexes, condition variables, futures and clean shutdown (see C++ concurrency basics).
- Memory: alignment, placement new, ownership and RAII (see RAII and smart pointers).
- Durability: append-only logs, checksums and atomic file replacement.
- Worst-case thinking: algorithms that stay linear on adversarial input.
- Invariants under load: property tests that hammer a system with thousands of operations.
The projects
Mergebay
A diff engine for Mergebay
Compute minimal line diffs with the longest common subsequence, then render them as unified-diff hunks with context, exactly like the tools reviewers already know.
- dynamic programming
- LCS
- unified diff format
- edge cases
Vaultline
A durable key-value store for Vaultline
Build Vaultline's embedded key-value store: an append-only log that survives crashes, checksums that catch corruption, and compaction that rewrites the log atomically.
- append-only logs
- crash recovery
- checksums
- atomic file replacement
Shardline
Sharding with a hash ring for Shardline
Replace modulo sharding with consistent hashing: a ring with virtual nodes that moves few keys when servers come and go, then replicas and weighted servers.
- consistent hashing
- ordered maps
- hash functions
- statistical testing
Relaybox
A message queue for Relaybox
Build the bounded, blocking, closable queue between Relaybox's receivers and senders: mutexes, condition variables, backpressure, shutdown, timeouts and batches.
- threads
- mutexes
- condition variables
- backpressure
Batchworks
A thread pool for Batchworks
Replace thread-per-job with a fixed pool of workers: a shared task queue, graceful shutdown, failure accounting, futures for results and a parallel_for.
- threads
- task queues
- futures
- shutdown semantics
Tickmark Exchange
An order book for Tickmark Exchange
Build the heart of an exchange: a limit order book with price-time priority, partial fills and O(1) cancels, then market orders, immediate-or-cancel and order amendments.
- ordered maps
- iterator stability
- invariants
- property-based testing
Sieve Mail
A safe regex engine for Sieve Mail
Write the regular-expression engine behind Sieve Mail's filter rules: a parser, Thompson's NFA construction and a simulation that runs in linear time, so no rule can hang the mail servers.
- parsing
- automata
- Thompson's construction
- worst-case complexity
Picking your first Summit project
- Want concurrency? Start with a message queue for Relaybox, then build a thread pool for Batchworks on the same ideas.
- Prefer systems and storage? A durable key-value store for Vaultline teaches write-ahead logs and crash recovery.
- Like algorithms? A safe regex engine for Sieve Mail builds Thompson's construction from scratch.
The order book for Tickmark Exchange combines several of these skills and makes a strong portfolio piece; see portfolio projects that impress employers.
Questions and answers
- What are good advanced C++ projects for a portfolio?
- Projects where correctness under pressure matters: a thread pool, a crash-safe storage engine, a memory allocator, an order matching engine or a regex engine with a worst-case guarantee. They show you understand concurrency, memory and failure modes.
- How do I test concurrent C++ code?
- Test the guarantees, not the timing: nothing lost or duplicated, every waiter woken on shutdown, no deadlock. Run the tests many times, and build once with -fsanitize=thread to catch data races.
Practise it in a project
These projects put this guide to work, with tickets, tests and code review.
Batchworks
A thread pool for Batchworks
Replace thread-per-job with a fixed pool of workers: a shared task queue, graceful shutdown, failure accounting, futures for results and a parallel_for.
- threads
- task queues
- futures
- shutdown semantics
Pixelforge
Memory pools for Pixelforge
Stop frame stutters in Pixelforge's engine with a fixed-size block allocator: an intrusive free list, alignment, misuse detection, then a typed object pool with RAII handles.
- manual memory management
- alignment
- placement new
- RAII and templates
Vaultline
A durable key-value store for Vaultline
Build Vaultline's embedded key-value store: an append-only log that survives crashes, checksums that catch corruption, and compaction that rewrites the log atomically.
- append-only logs
- crash recovery
- checksums
- atomic file replacement
Tickmark Exchange
An order book for Tickmark Exchange
Build the heart of an exchange: a limit order book with price-time priority, partial fills and O(1) cancels, then market orders, immediate-or-cancel and order amendments.
- ordered maps
- iterator stability
- invariants
- property-based testing
Read next
- Portfolio projects that impress employers (and how to present them)
What hiring managers look for in a developer portfolio, which kinds of projects show it, and how to present them: README, tests, design notes and a clean history.