Event-driven Commerce Platform
Orders, stock, and payment with transactions, outbox, auditing, cache, and queues.
Backend Software Engineer
Ruan Fernandes
APIs, data, and asynchronous systems for reliable products in production.
Backend first. Complete product.
I build APIs, data models, and asynchronous processes with TypeScript and Node.js, prioritizing clarity, consistency, and operations.
React and Next.js help demonstrate real flows and deliver a good experience. The core of my work stays in architecture, data, and service reliability.
Systems that put difficult decisions into the design.
Every project starts from a real operational concern and makes its technical choices explicit.
Multi-tenant Operations API
Organization isolation, RBAC, GraphQL, rotating tokens, and asynchronous jobs.
Workflow and Approval Engine
Versioned definitions, durable workers, retries, compensation, and human approval.
Backend Engineering Lab
Executable references for idempotency, locks, outbox, circuit breakers, and graceful shutdown.
The interface supports the system. It does not replace engineering.
I use frontend work to make decisions and flows verifiable, while important complexity stays where it belongs.
Model boundaries
Transactional invariants, tenant isolation, and rules that survive concurrent work.
Assume duplicate delivery
Outbox, idempotency, retry, and recovery are part of the design from the first decision.
Operate with context
Logs, metrics, tracing, and tests make system behavior understandable in production.
Let us talk about systems that need to keep standing.
I am open to backend opportunities and products where architecture, reliability, and execution matter.