Nahom Zewdu

Current Focus

Event-Driven Architecture & Async Systems

Active

Building systems that respond to events rather than requests requires rethinking common patterns. The challenge is managing ordering guarantees, deduplication, and late arrivals while keeping the system simple to reason about. Currently exploring how to model event-driven workflows in Go and Python, with emphasis on testability and operational clarity.

Focus Areas

  • Message queue design patterns and operational tradeoffs
  • Event schema versioning and backward compatibility
  • Distributed tracing and observability for async workloads
  • Consumer lag monitoring and failure recovery

Developer Tooling & Automation Pipelines

Active

Building tools that make developers more productive. This includes designing clean APIs, reducing cognitive load, and making common patterns explicit. Interested in automation frameworks that handle edge cases gracefully and provide good failure visibility.

Focus Areas

  • Building CLIs that reduce boilerplate and automate repetitive tasks
  • Designing automation pipelines that integrate external services
  • Task scheduling systems for complex workflows
  • Observability and monitoring for automated processes

Distributed Systems at Scale

Exploring

Understanding how systems behave under real-world constraints: network partitions, partial failures, and operational complexity. Studying how companies scale systems from thousands to millions of requests per second, and what decisions enable that growth.

Focus Areas

  • Consistency models and tradeoffs (strong vs eventual)
  • Consensus algorithms and their practical implications
  • Database design for distributed workloads
  • Cost-aware infrastructure and resource optimization

Production Systems & Observability

Active

The gap between what code does in tests and what it does in production is where most problems live. Focusing on systems that are easy to operate, debug, and improve. This means designing for observability from the start, not bolting it on later.

Focus Areas

  • Structured logging and log aggregation patterns
  • Metrics collection and alerting strategies
  • Incident response and postmortem culture
  • Making operational tradeoffs explicit in code