NETGEAR SUBSCRIPTION SYSTEM
Principal Engineer & Cloud Architecture Lead
Principal Engineer & Cloud Architecture Lead
Large-scale modernization of the subscription platform serving hundreds of thousands of users and tens of millions of devices.
THE CHALLENGE :
THE CHALLENGE :
THE CHALLENGE :
The existing subscription systems had grown organically under Conway’s Law, resulting in fragmented data, multiple sources of truth, and poor data governance. Multiple organizations across the company (engineering, IT, customer service, finance, and marketing) depended on this data, making a full rewrite extremely risky. The core challenge was to establish clean architecture and governance without disrupting critical business operations or requiring a high-risk cutover.
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
A green-field rebuild was technically straightforward but organizationally dangerous. I focused on reducing risk while still delivering a fundamentally better system.
Key decisions included:
Using the Strangler pattern to place the new architecture behind existing APIs, allowing incremental replacement
Implementing a “shadow mode” where the new system processed data in parallel with the old one for validation before taking over
Avoiding a large-scale data migration by gradually assuming responsibility for new subscriptions and then renewals
Creating new architectural standards, testing practices, deployment pipelines, and infrastructure-as-code approaches that could be reused
Investing heavily in stakeholder alignment across multiple organizations that had competing priorities
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
I led the design and delivery of the new subscription system while working across engineering, IT, and business teams. The solution included:
A clean, governed subscription service that became the single source of truth
Incremental cutover using the Strangler pattern and shadow mode to validate correctness before switching traffic
New CI/CD, testing, and infrastructure practices that improved reliability and speed of delivery
Close collaboration with consumer teams so they could continue using familiar APIs while the underlying system was replaced
Clear communication and risk management with stakeholders who were initially resistant to change
By sequencing the rollout carefully (new subscriptions first, then renewals), we allowed the data to migrate itself over time and avoided a risky big-bang migration.
RESULTS & IMPACT :
RESULTS & IMPACT :
RESULTS & IMPACT :
Increased subscription-to-service delivery accuracy from ~90% to >99%
Improved API response times from >1 second to sub-100ms
Established a single source of truth for subscription data across the company
Significantly reduced data inconsistencies and governance issues
Delivered the new system with minimal disruption to ongoing operations
Created reusable architectural and delivery practices that improved how future systems were built
Built alignment across previously siloed organizations
WHAT I LEARNED :
WHAT I LEARNED :
WHAT I LEARNED :
Large-scale platform change is rarely just a technical problem. The harder work is creating enough shared understanding and trust across teams that people are willing to accept a better long-term design even when it creates short-term inconvenience. Technical elegance only succeeds when paired with deliberate stakeholder management and risk reduction.
TECHNOLOGIES :
TECHNOLOGIES :
TECHNOLOGIES :
Cloud architecture · AWS · Data governance · Microservices · Infrastructure as Code · CI/CD · Strangler pattern
NETGEAR SUBSCRIPTION SYSTEM
Principal Engineer & Cloud Architecture Lead
Principal Engineer & Cloud Architecture Lead
Large-scale modernization of the subscription platform serving hundreds of thousands of users and tens of millions of devices.
THE CHALLENGE :
THE CHALLENGE :
THE CHALLENGE :
The existing subscription systems had grown organically under Conway’s Law, resulting in fragmented data, multiple sources of truth, and poor data governance. Multiple organizations across the company (engineering, IT, customer service, finance, and marketing) depended on this data, making a full rewrite extremely risky. The core challenge was to establish clean architecture and governance without disrupting critical business operations or requiring a high-risk cutover.
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
A green-field rebuild was technically straightforward but organizationally dangerous. I focused on reducing risk while still delivering a fundamentally better system.
Key decisions included:
Using the Strangler pattern to place the new architecture behind existing APIs, allowing incremental replacement
Implementing a “shadow mode” where the new system processed data in parallel with the old one for validation before taking over
Avoiding a large-scale data migration by gradually assuming responsibility for new subscriptions and then renewals
Creating new architectural standards, testing practices, deployment pipelines, and infrastructure-as-code approaches that could be reused
Investing heavily in stakeholder alignment across multiple organizations that had competing priorities
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
I led the design and delivery of the new subscription system while working across engineering, IT, and business teams. The solution included:
A clean, governed subscription service that became the single source of truth
Incremental cutover using the Strangler pattern and shadow mode to validate correctness before switching traffic
New CI/CD, testing, and infrastructure practices that improved reliability and speed of delivery
Close collaboration with consumer teams so they could continue using familiar APIs while the underlying system was replaced
Clear communication and risk management with stakeholders who were initially resistant to change
By sequencing the rollout carefully (new subscriptions first, then renewals), we allowed the data to migrate itself over time and avoided a risky big-bang migration.
RESULTS & IMPACT :
RESULTS & IMPACT :
RESULTS & IMPACT :
Increased subscription-to-service delivery accuracy from ~90% to >99%
Improved API response times from >1 second to sub-100ms
Established a single source of truth for subscription data across the company
Significantly reduced data inconsistencies and governance issues
Delivered the new system with minimal disruption to ongoing operations
Created reusable architectural and delivery practices that improved how future systems were built
Built alignment across previously siloed organizations
WHAT I LEARNED :
WHAT I LEARNED :
WHAT I LEARNED :
Large-scale platform change is rarely just a technical problem. The harder work is creating enough shared understanding and trust across teams that people are willing to accept a better long-term design even when it creates short-term inconvenience. Technical elegance only succeeds when paired with deliberate stakeholder management and risk reduction.
TECHNOLOGIES :
TECHNOLOGIES :
TECHNOLOGIES :
Cloud architecture · AWS · Data governance · Microservices · Infrastructure as Code · CI/CD · Strangler pattern
NETGEAR SUBSCRIPTION SYSTEM
Principal Engineer & Cloud Architecture Lead
Principal Engineer & Cloud Architecture Lead
Large-scale modernization of the subscription platform serving hundreds of thousands of users and tens of millions of devices.
THE CHALLENGE :
THE CHALLENGE :
THE CHALLENGE :
The existing subscription systems had grown organically under Conway’s Law, resulting in fragmented data, multiple sources of truth, and poor data governance. Multiple organizations across the company (engineering, IT, customer service, finance, and marketing) depended on this data, making a full rewrite extremely risky. The core challenge was to establish clean architecture and governance without disrupting critical business operations or requiring a high-risk cutover.
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
APPROACH & KEY DECISIONS :
A green-field rebuild was technically straightforward but organizationally dangerous. I focused on reducing risk while still delivering a fundamentally better system.
Key decisions included:
Using the Strangler pattern to place the new architecture behind existing APIs, allowing incremental replacement
Implementing a “shadow mode” where the new system processed data in parallel with the old one for validation before taking over
Avoiding a large-scale data migration by gradually assuming responsibility for new subscriptions and then renewals
Creating new architectural standards, testing practices, deployment pipelines, and infrastructure-as-code approaches that could be reused
Investing heavily in stakeholder alignment across multiple organizations that had competing priorities
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
SOLUTION & IMPLEMENTATION :
I led the design and delivery of the new subscription system while working across engineering, IT, and business teams. The solution included:
A clean, governed subscription service that became the single source of truth
Incremental cutover using the Strangler pattern and shadow mode to validate correctness before switching traffic
New CI/CD, testing, and infrastructure practices that improved reliability and speed of delivery
Close collaboration with consumer teams so they could continue using familiar APIs while the underlying system was replaced
Clear communication and risk management with stakeholders who were initially resistant to change
By sequencing the rollout carefully (new subscriptions first, then renewals), we allowed the data to migrate itself over time and avoided a risky big-bang migration.
RESULTS & IMPACT :
RESULTS & IMPACT :
RESULTS & IMPACT :
Increased subscription-to-service delivery accuracy from ~90% to >99%
Improved API response times from >1 second to sub-100ms
Established a single source of truth for subscription data across the company
Significantly reduced data inconsistencies and governance issues
Delivered the new system with minimal disruption to ongoing operations
Created reusable architectural and delivery practices that improved how future systems were built
Built alignment across previously siloed organizations
WHAT I LEARNED :
WHAT I LEARNED :
WHAT I LEARNED :
Large-scale platform change is rarely just a technical problem. The harder work is creating enough shared understanding and trust across teams that people are willing to accept a better long-term design even when it creates short-term inconvenience. Technical elegance only succeeds when paired with deliberate stakeholder management and risk reduction.
TECHNOLOGIES :
TECHNOLOGIES :
TECHNOLOGIES :
Cloud architecture · AWS · Data governance · Microservices · Infrastructure as Code · CI/CD · Strangler pattern