Who is Fernando F. Azevedo?

Fernando F. Azevedo is a Senior Solutions Architect at Banco Itaú with 16+ years of experience across AWS, event-driven architecture, DevSecOps, Data Mesh, AI and financial systems.

What technical topics does Fernando work with?

Fernando works with AWS, Kubernetes, Kafka, Data Mesh, Amazon Bedrock, RAG, DevSecOps, observability, financial systems and architecture communication using C4, ADRs and trade-off analysis.

Is Fernando available for professional conversations?

Fernando is currently building at Banco Itaú and is open to thoughtful conversations about architecture, cloud, AI, engineering leadership, community, podcasts and technical collaboration.

Learning path · Trilha

Financial Systems

Core banking, payments and fintech-grade systems — correctness, compliance and resilience where money is on the line.

The path· 3

1Expert 9 minModern KYC: Serverless, AI and Audit Trails in Financial ServicesKYC (Know Your Customer) is evolving from an overnight batch process into an event-driven pipeline with AI-assisted decisions and immutable audit trails. This shift is not merely technical — it redefines how solution architects think about compliance, latency and cost in regulated financial environments. In this briefing, I analyze the signal, the emerging patterns and how to position your architecture for this transition.
2Expert 9 minAML Alert Triage with Governed AI: Architecture and Trade-offsAutomating AML alert triage with generative AI is technically feasible, but the distance between a working prototype and an auditable financial system is vast. In this article, I analyze the real architecture behind this automation — the orchestration mechanisms, the silent failure points, and the design decisions that separate a regulatorily defensible system from one that will fail a BACEN or FinCEN audit.
3Expert 9 minLambda Response Streaming for Real-Time Pricing EnginesLambda response streaming fundamentally changes the serverless execution contract by allowing bytes to be flushed to the client before the function completes — with deep implications for real-time pricing engines. In this analysis I dissect the internal mechanism, the failure modes documentation underemphasizes, and the architecture decisions that separate a prototype from a production financial system.

Deep-dive studies

design-docDesign Doc: Multi-Region Active-Active Payments APIThis document proposes a multi-region active-active architecture for a critical payments API, targeting near-zero RTO/RPO, deterministic conflict resolution in data replication, and a phased rollout that minimizes operational risk. The design is grounded in real financial engineering principles and AWS patterns, with explicit trade-offs between consistency, latency, and cost.adrADR: Aurora vs DynamoDB for a Double-Entry Ledger in Core BankingThis ADR evaluates Aurora PostgreSQL and DynamoDB as the persistence engine for a double-entry ledger in a core banking system, weighing strong consistency, access patterns, auditability, and cost. The decision favors Aurora with date-range partitioning and an immutable event layer, acknowledging the horizontal scaling constraints that choice imposes.adrADR: Modular Monolith vs Microservices in a Greenfield FintechAn early-stage fintech faces the classic architecture decision: go straight to microservices or build a modular monolith first. This ADR examines the real forces at play — team size, validation speed, blast radius, and operational cost — and records the decision with its concrete consequences.postmortemCloudflare 2019: The Regex That Took Down a Global NetworkOn July 2, 2019, a single WAF rule containing a regex with catastrophic backtracking saturated 100% of CPU across all Cloudflare servers globally, taking down services for approximately 27 minutes. The incident exposed critical failures in the rule deployment process, the absence of protection against algorithmic complexity, and the insufficiency of the testing pipeline to detect pathological patterns.teardownStripe: API Design and Idempotency KeysAn in-depth technical analysis of how Stripe solved the problem of safe retries in payment APIs using idempotency keys, request state storage, and rate limiting — design decisions that became an industry reference.postmortemKnight Capital (2012): US$440M in 45 Minutes from a Partial DeploymentOn August 1, 2012, Knight Capital lost US$440 million in under an hour due to a partial deployment that left legacy code active on one of eight trading servers. A reused configuration flag activated an obsolete function that fired millions of unintended orders into the US market. The incident is a canonical case of how deployment process failures and the absence of kill-switch mechanisms can destroy a company in minutes.

Open source to explore

aws-event-driven-finops-platformEvent-driven AWS banking reference architecture with FinOps, security, and a live frontend.DeskbuddyESP32 touchscreen smart desk dashboard — firmware, web UI, and browser installer in one repo.