👋 Hi, I'm Lucas

Technical solutions in production

• Microservices architecture for 100+ stores operation

  Context: Sales, after-sales, and external integration flows were highly coupled, increasing deployment risk and outage windows.

  • —Split domains into services with clear ownership and versioned contracts.
  • —Introduced RabbitMQ/Kafka for asynchronous workloads and failure isolation.
  • —Implemented idempotent consumers and retry policies with backoff for critical events.

  Outcome: Lower deployment impact, fewer failures caused by synchronous dependencies, and more predictable throughput during peak traffic.

• API contract standardization across squads

  Context: Inconsistent endpoint semantics and unmanaged changes were breaking internal and external integrations.

  • —Defined REST/GraphQL standards for error semantics, versioning, and observability.
  • —Added contract validation in CI pipelines to prevent unplanned breaking changes.
  • —Created concise technical documentation to accelerate onboarding and alignment.

  Outcome: Less integration rework, faster onboarding, and stronger API consumption stability across systems.

• Continuous delivery hardening for critical environments

  Context: Manual release process was increasing operational risk and slowing down production delivery.

  • —Automated CI/CD pipelines with quality gates (lint, tests, build, and security checks).
  • —Containerized services and standardized rollout strategy to reduce regression risk.
  • —Centralized telemetry to detect performance degradation immediately after deploy.

  Outcome: Shorter lead time, safer and more frequent releases, and faster incident recovery.