Designing and building an event-driven microservices architecture in Rust from the ground up — the flagship engineering effort of my time at L'una S.r.l. This isn't a CRUD backend: it's a distributed, async-first system built for real-time data flow, using Valkey as the event backbone (streams/queues) and AWS S3 for durable persistence, with Tokio powering fully asynchronous, scalable services under the hood. I'm also leading the early architectural groundwork for a Kubernetes-based deployment, and building out full observability into the stack with Grafana, Alloy, Loki, and Tempo — so every event flowing through the system is traceable end to end. This project is where I've pushed hardest into systems-level Rust: performance, correctness, and observability all designed in from day one, not bolted on after.

1. Fleet Tracking & Route Management System — Backend in Spring Boot, frontend in Angular, mobile app in Expo (React Native), for a client managing street-sweeping vehicles. Routes were designed and assigned to vehicles from the Angular management dashboard; the mobile app, linked to a specific vehicle, showed the assigned route (not turn-by-turn navigation, but the streets to be swept). The dashboard displayed the vehicle's progress along the route in real time via WebSocket, as well as historical route data.

2. Legacy System Maintenance — Bug fixing (both frontend and backend) on a legacy management system built in Java and Angular, based on issues reported by the client.

• Description: A minimal decentralized exchange built as a Solana on-chain program (Anchor). Users deposit two SPL tokens, place buy/sell orders, and the program matches and settles compatible orders automatically via escrow PDAs.
• Key Concepts: Cross-Program Invocation (CPI), Program Derived Addresses (PDA), SPL Token program, on-chain order matching logic.
• Why it's a good project: Combines Web3/Solana skills with order-matching logic similar to real trading systems, under the stricter constraints of a blockchain execution environment.
• Repo: solana-mini-dex

• Description: An embedded database engine built from scratch: data persisted to disk in fixed-size pages, indexed with a B-Tree for efficient lookups, supporting insert/get/delete/range-scan.
• Key Concepts: B-Tree data structure, page-based file I/O, serialization, write-ahead logging for durability.
• Why it's a good project: Demonstrates deep understanding of on-disk data structures and storage engine internals, complementing ORM-level work like ducklake-orm.
• Repo: mini-db-btree

• Description: A load-testing and observability CLI for microservices that communicate through Valkey (pub/sub/streams) instead of direct HTTP. Measures end-to-end latency and consumer lag across the whole pipeline, with a live terminal dashboard.
• Key Concepts: Pub/Sub and Streams, consumer lag/backpressure, async concurrency with Tokio, distributed observability.
• Why it's a good project: Goes beyond generic HTTP load testing to address real event-driven architecture problems, directly relevant to Valkey/Redis-based infrastructure.
• Repo: valkey-loadtest

• Description: A key-value store replicated across multiple nodes that stays consistent even if a node crashes, implementing the Raft consensus algorithm for leader election and log replication.
• Key Concepts: Leader election, log replication, quorum/majority agreement, term numbers.
• Why it's a good project: Hands-on understanding of consensus and replication, the same category of problem underlying real distributed databases and clustered Valkey/Redis deployments.
• Repo: raft-kv-store

Note: these competency levels are subjective — they reflect my own self-assessment and how confident I personally feel with each technology, not a formal or standardized scale.

• Expert: I have completed numerous complex projects independently.
• Proficient: I have successfully completed several medium-complexity projects.
• Competent: I have used the technology in projects for small/medium specific tasks.
• Familiar: I have foundational knowledge and have done personal experiments.
• Exploring: I’ve just taken a quick look at this technology.