Alan Vazquez

Specification

I build backend systems and keep the record of every change.

Seven years on Go, Python, and Rust, in fintech — close to FIX order flow. Every entry here carries its date, its decisions, and its lifecycle state.

Role
Software Engineer · Trii
Domain
Fintech · FIX · Investments
Stack
Go · Python · Rust
Experience
7 years
contact@alanv.me GitHub

Exploded view

The part that changed what fixlog can do

Exploded view of fixlog's pipeline Five stacked stages drawn in isometric outline: memory-mapped read, layout sniffing, message parsing, indexed lookup, and terminal viewer. Four stages are drawn as gray ghosts, already assembled; the indexed lookup is drawn in red above its empty dotted seat, with two dotted arrows pointing into it. P-01 MMAP zero-copy P-02 SNIFF layout P-03 PARSE 8=FIX scan P-04 INDEX rayon · hot-tag P-05 TUI ratatui
Already assembled The part that changed
1:1 P-04 · INDEX · rayon

An equality filter over one million messages: ~477 ms → ~156 µs.

Parts list

Across every published entry, not this drawing

fixlog streams FIX logs without loading them: it memory-maps the file, sniffs the layout, scans message boundaries, renders. The decisive part is the indexed hot-tag lookup — with it, an equality filter stops scanning every message.

All projects

Revision log

Dated entries, newest first

Each entry keeps its date and its state. A retired one keeps its page and points at what replaced it.

  1. fixlog

    Project

  2. DotCLI

    Project

Contact

Next step: write to me.

For a backend role, a technical review, or a question about any entry here.

contact@alanv.me GitHub LinkedIn