The Saga Pattern in Microservices: Why Distributed Transactions Lose Atomicity
What I learned comparing monoliths and microservices, with a real-world loan document pipeline.
Read on Medium ↗Houston, TX · Open to new opportunities
Senior Platform & Cloud Infrastructure Engineer
I build the foundations other engineers ship on — AWS networking, identity, Terraform modules, CI/CD, and observability — and lately, the developer tooling that makes that platform easier to use. That same craft is what I'm bringing to trading technology: platforms and pipelines that take quant research from notebook to production without losing rigor.
I'm a platform and cloud infrastructure engineer with about seven years of experience across fintech, cybersecurity, and investment management.
My career arc runs from ML platform infrastructure at Vanguard, to cloud consulting and data pipelines at Slalom, to SRE/DevOps for multi-regional Kafka, Elasticsearch, and EKS at Trellix — and now to large-scale cloud re-platforming and platform engineering for a fintech, through Evolv Consulting. Lately I've been building developer-facing tooling: reusable Terraform modules, an AI chatbot, and an MCP server.
My consulting background means I'm comfortable with client stakeholders, ambiguous requirements, and translating business needs into infrastructure that actually ships. Core focus areas: AWS cloud infrastructure, platform engineering, Terraform, Python automation, distributed systems, networking, IAM/identity, CI/CD, observability, and on-call incident response.
Outside work I trade stocks and options and manage my own portfolio. That same instinct is what pulled me toward quantitative finance: a strategy is only as trustworthy as the data, backtests, and infrastructure behind it — and that's where I've spent my career. I'm now building the other half of the picture through the MIT MicroMasters in Finance and the Wall Street Quants program, working hands-on with Python-based research workflows: data manipulation, backtesting, portfolio weighting, and performance evaluation.
Working at that intersection — as a quant developer or front-office engineer — is something I'd love to do. But at my core I'm a software engineer, and that's where I want my career to be: building the platforms, pipelines, and tooling that turn ambitious ideas into production systems, whether that's cloud infrastructure or quant research carried from notebook to production without losing rigor.
Evolv Consulting — client: SoFi, an all-in-one digital platform for banking, lending, and investing
terraform state mv migration of existing resources.ForAllValues:StringEquals conditions for shared multi-app service roles.Trellix — cybersecurity: threat intelligence and detection
Slalom — global business and technology consulting firm
Vanguard — investment management
A Python 3.10+ CLI (Typer + Rich), published on PyPI as iacgen, that generates
opinionated Terraform blueprints for AWS — VPC, EKS, ALB, Kubernetes Service —
from a single command or YAML presets.
Evolv internal hackathon (2025). On a 2–4 person team, I split work between the Snowflake data layer — schema and detection queries — and the Streamlit dashboard.
A self-contained, EC2-based payments system: three FastAPI services (payments API, ledger, fraud-check) on their own hosts, discovered by DNS, deployed by GitHub Actions through S3 and SSM — with fault injection and load generation built in.
A push-based configuration management tool built from scratch in Bash to learn how Ansible works under the hood — agentless, host-node architecture over key-based SSH. A learning experiment, by design.
I write about infrastructure, distributed systems, and Python — latest from Medium.
What I learned comparing monoliths and microservices, with a real-world loan document pipeline.
Read on Medium ↗When to reach for threads over async: a practical guide to ThreadPoolExecutor for I/O-bound workloads like HTTP calls and CRUD actions.
Read on Medium ↗Part 6 of the iacgen build series: packaging the Terraform blueprint generator and publishing it to PyPI.
Read on Medium ↗Nana handled client stakeholder conversations with grace, navigated risk well, and stepped outside his comfort zone — AWS infrastructure, complex SQL, and vendor API integrations — on a project far more complex than its initial dashboard scope. The team's work earned an 8-week extension.
"I don't care what we need to do to keep this team on board but let's make that happen."
Nana engaged disparate client team members to refine unclear requirements with little oversight, made solid backend contributions, and kept a positive, learner's attitude and poise under pressure.
The fastest way to reach me is email — I read everything.
Based in Houston, TX · Remote-friendly