SYSTEM ONLINE / TORONTO, CANADA

SOFTWAREENGINEER.

I'm Domenico Nota, a University of Toronto Computer Science student building backend systems, distributed infrastructure, and AI applications.

PORTFOLIO // VERSION 2026
43.6° N
79.4° W
EXPLORE MY WORK
00 / 05
01ABOUTTHE HUMAN BEHIND THE SYSTEM

COMPUTER SCIENCE.
PRACTICAL SYSTEMS.

I'm a Computer Science student at the University of Toronto, with a minor in Mathematics. What drives me isn't just making software work. It's understanding complex problems deeply enough to make them feel simple.

From low-level infrastructure to AI-powered workflows, I like taking ideas from rough architecture to working systems that people can actually rely on.

2027EXPECTED GRADUATION
U OF TCOMPUTER SCIENCE + MATH
● ACTIVEBUILDING / LEARNING
TORONTO, CANADAB.SC. COMPUTER SCIENCE · MAY 2027↓
02EXPERIENCEREAL-WORLD IMPACT

FROM IDEAS
TO IMPACT.

The best architecture proves itself in production. Here's where my work meets the real world.

JAN 2026 — NOW CURRENT
01 / SOFTWARE ENGINEER INTERN

Bid Engine

Building the intelligence behind construction tender estimation: document extraction, agent tooling, retrieval, and cloud-native event pipelines.

94%TENDER EXTRACTION COVERAGE
91%TOP-1 SKU MATCH ACCURACY
6h → 8mCATALOG ONBOARDING TIME
2,400/minINVITATIONS THROUGHPUT
PythonSpring BootLangGraphKafkaAzure AKSpgvector
JAN — APR 2025
02 / STUDENT MACHINE LEARNING ENGINEER

University of Toronto

Owned the full stack of a real-time market simulation platform, connecting live-data ingestion, forecasting workflows, and a React experience.

14 REST ENDPOINTS10K+ MARKET TICKS / MIN87% LOWER FORECAST REFRESH COST
ReactFlaskMongoDBMLGitHub Actions
SEP — DEC 2024
03 / WEB DEVELOPER

UofT.ai

Built an accessible, responsive React application for 700+ monthly users and helped ship it with automated deployment to AWS EC2.

ReactChakra UIAWS EC2CI/CD
03SELECTED PROJECTSARCHITECTURE & IMPLEMENTATION

SELECTED
PROJECTS.

Explore the architecture, implementation choices, and testing behind each project.

PROJECT // 001OBSERVABILITY
01 / SYSTEMS + INFRASTRUCTURE

LogStream

A local log pipeline with bounded Rust collection, Kafka buffering, idempotent PostgreSQL writes, and a React explorer.

AT-LEAST-ONCE AFTER KAFKA ACCEPTANCECURSOR SEARCH PAGINATION
PROJECT // 002RESILIENCE
02 / DISTRIBUTED ARCHITECTURE

Fault-Tolerant
Order System

Event-driven order, payment, inventory, and shipping services engineered to recover gracefully when things break.

4 SERVICE DOMAINSOUTBOX RELIABLE EVENT PUBLICATION
PROJECT // 003DISCOVERY
03 / SEARCH ENGINEERING

Distributed
Search Engine

Full-text search with global TF-IDF ranking, consistent-hash routing, persisted shards, and explicit partial results.

3 SHARD NODESGLOBAL TF-IDF RANKING
01 / LogStream Architecture & delivery guarantees

Problem

Collect application logs, absorb database interruptions, and make stored events searchable without silently advancing past failed writes.

Implementation

A Rust agent sends bounded HTTP batches to a Go API. Kafka buffers accepted events; a separate Go worker owns persistence and offset commits. PostgreSQL deduplicates repeated event IDs.

Tradeoff

At-least-once delivery begins after Kafka acceptance. The agent uses memory rather than a disk spool, so events can be lost before that boundary. Cursor pagination keeps query traversal stable.

Verification

The repository includes a deterministic end-to-end demo that checks one event through the pipeline and asserts that repeated delivery stores one row. No throughput claim is made here without a recorded benchmark run.

Follow a log event

Select a stage to inspect its responsibility. This is an architecture walkthrough, not a live backend.

Rust agent — bounded collection

Tails log files, assigns stable event IDs, and sends bounded batches through HTTP. Retries reuse the same IDs; the in-memory queue is not a durable disk spool.

Read path: React explorer → Go query API → PostgreSQL. Poison records: Go worker → Kafka dead-letter topic.

View LogStream repository ↗
02 / Order system Recovery & consistency

Role: Code contributor · Repository: tusharra0/Fault-Tolerant-Order-System

Problem

Coordinate order, payment, inventory, and shipping when messages can be delivered more than once and individual stages can fail.

Implementation

Four service domains own separate databases. Transactional outboxes publish events through RabbitMQ; idempotent consumers and Saga-style compensation handle repeated deliveries and downstream failures.

Tradeoff

At-least-once delivery and eventual consistency avoid requiring one transaction across all services, but require deduplication, outbox workers, and explicit compensation logic.

Measured context

The repository reports a 2026-08-08 Locust run on a GitHub-hosted Ubuntu runner: 20 users, two minutes, 2,370 requests, 19.905 requests/sec, 160 ms p95, and zero request failures. This measures API acceptance, not end-to-end order completion.

Order API → transactional outbox → RabbitMQ → payment → inventory → shipping
Status events return to the order projection; failures can trigger refunds and reservation releases.

Local Docker Compose implementation with simulated domain services; not a claim of a live production deployment.

View order-system repository & measured results ↗
SOURCE CODE, DESIGN DECISIONS, AND TESTS.EXPLORE MY GITHUB ↗
04TECHNICAL SKILLSTOOLS OF THE TRADE

TECHNICAL
SKILLS.

Languages and frameworks are means to an end. I choose the ones that make a system more useful, reliable, and clear.

BACKEND ENGINEERING

Python · Java · SQL · FastAPI · Spring Boot · REST APIs

D/NTOOLKIT
STACK: 04 / 04
SELECT CATEGORY TO DECODE
05THE NEXT CHAPTEROPEN CHANNEL

LET'S BUILD
WHAT'S NEXT.

Interested in discussing a software engineering opportunity? Get in touch.

START A CONVERSATION
SYSTEM DECODED

Read full case study ↓
VIEW SOURCE ↗