Skip to content
Back to work

Production case

Grupo Bandeirantes

Modernization of six Grupo Bandeirantes portals, with a shared architecture and no service interruption during migration.

Responsibility
Software engineering & IT management
Organization
Grupo Bandeirantes
Period
2024

Production evidence

Portals migrated
6+
Grupo Bandeirantes editorial portals.
Migration downtime
0s
During the transition to the new architecture.
Distribution partnership
1
Vivo, for content distribution.

The platform in use

Overview

I led the modernization of BandSports, BandNews TV, Arte 1, Sabor & Arte, Terra Viva, and Agro+. The work combined software architecture, coordination across design and engineering, and production oversight. The scope also included content distribution through the Vivo partnership.

Challenge

Replace legacy systems while all six portals continued serving their audiences. The migration needed to balance independent delivery, consistency across teams, and traffic spikes during elections and sports events.

Architecture & solution

I defined a shared foundation in Next.js and Go, with NestJS for supporting services and independent deployments for each portal. On AWS, load balancing, WAF, gradual rollout, and automated rollback helped control the risk of each release.

Web experience
Next.js · React · TypeScript
Services
Go · NestJS · shared components
Operations
AWS · WAF · load balancing · gradual rollout

Engineering decisions

  1. Share the technical foundation while keeping deployments independent, so standardizing components did not require migrating every portal at once.
  2. Use Go for backend throughput and latency requirements, Next.js for the web layer, and NestJS for supporting services.
  3. Use gradual rollout and automated rollback, making service continuity a requirement of the deployment strategy.
  4. Use AWS for edge protection and load balancing to support changes in audience demand.

My contribution

I owned the architecture and technical delivery. I coordinated four squads, aligned priorities and schedules with leadership, and oversaw deployments. I also worked on the code to resolve performance bottlenecks during critical migration stages.

Outcomes

All six portals moved to the new architecture without service interruption during migration. A common foundation simplified maintenance while allowing each team to evolve its portal independently.

  • Six portals migrated without downtime during the transition.
  • Shared components and lower maintenance costs for the technical foundation.
  • Content distribution included in the Vivo partnership.

Lessons learned

  • Legacy migrations require business alignment alongside technical decisions. A consistent architecture alone cannot resolve competing priorities.
  • Releasing in stages makes risk easier to control. The rollback plan belongs in the delivery process from the start.

Technology & platform

  • Next.js
  • Go
  • NestJS
  • React
  • AWS
  • Load Balancing
  • WAF
  • TypeScript

Products under management

I led these 9 products from conception through development, deployment, and ongoing production support.

Editorial portals

Newco Play ecosystem