Case study · limited disclosure
Cloud migration and observability
A production migration from multiple backend services toward a clearer AWS-based foundation with stronger operational visibility.
Recreated visual for portfolio presentation. Not the original production interface.
Disclosure: Limited-disclosure case study. Architecture is intentionally generalized; no private schema, credentials, infrastructure diagrams, or implementation details are included.
Situation
Filament needed to move production responsibilities away from multiple backend-as-a-service providers and toward an AWS-based foundation with clearer operational ownership.
Constraints
Migration work changes a live system while preserving its behavior. Database organization, security, monitoring, and analytics all have to move in coordinated steps without exposing private infrastructure or customer data.
Role
As a Software Engineer, Jairo contributed to provider migration, database redesign and reorganization, monitoring, security, and analytics integrations during March through May 2026.
Technical decisions
The work treated observability as part of the migration rather than a later add-on. Sentry and Datadog improved failure visibility, while analytics integrations were incorporated deliberately alongside infrastructure and data changes.
Execution
The migration was approached as a sequence of bounded changes with explicit operational signals. This portfolio account intentionally omits private schemas, credentials, topology, and unapproved implementation details.
Outcome
The engagement established a clearer cloud direction and stronger visibility into production behavior. Exact performance or reliability metrics are not published because they have not been approved for public use.
Learning
A migration is complete only when the team can understand and operate the resulting system. Architecture, data organization, security, and monitoring belong in the same delivery conversation.