Speaker
Abstract
In this age of an interconnected world, One Network helps customers to simplify deployment of their products and services by providing a unified service and policy oriented network architecture that breaks down the boundaries of public and private clouds, different runtimes and traffic patterns.
Google Cloud networking evolved organically over time, which created friction for feature parity and interoperability between cloud products due to different infrastructure and policy enforcement points for internet traffic, service to service communication, for Kubernetes, serverless or VM-based runtimes and communication with on-prem and other public clouds.
In this presentation we will discuss One Network as a unified service networking architecture with the focus on:
Open Source proxies and control APIs as building blocks for cross runtimes, cross path and across public and private clouds
Uniform policies and policy enforcement on each path and secure by default application deployments
Opening converged network infrastructure to third party security, API management and traffic management SaaS developers
Interview
These days I work on evolving GCP from organically grown 300 Cloud products into a cohesive platform. This includes efforts such as One Network, and also efforts that we call One Producer Stack to enable developers write code once and run it on multiple environments where GCP exists. I am also working on AppHub as our GCP-wide effort to evolve GCP from infrastructure platform to an Application and Services platform
One Network project is 4 years in running and has been based on a previously running 3 year project we called internally One Proxy. Overall the effort is 7 years old and we thought it is time to share our learnings and accomplishments of building unified service networking architecture across GCP and Google internal production environment.
Software engineers interested in architecture of massively scalable distributed systems and platforms.
Understanding that unification of software infrastructure pays off with benefits in development velocity, ability to control distributed environments via policies.
Topics
QCon San Francisco 2024 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
From the same track
Wednesday 20 November
10:35 Ballroom A Session Thinking Like an Architect Gregor Hohpe Author of "Enterprise Integration Patterns" and "The Software Architect Elevator", Cloud Architect, Member of IEEE Software Advisory Board, Previously @AWS, @Google, and @Allianz Are architects supposed to be the smartest people on the team, making all the important decisions for developers to fill in the blanks? Certainly not. Rather, architects make everyone else smarter, for example by sharing decision models or revealing blind spots. 11:45 Ballroom A Session Architecture One Network: Cloud-Agnostic Service and Policy-Oriented Network Architecture Anna Berenberg Engineering Fellow, Foundation Services, Service Networking, @Google Cloud, Co-Author of "Deployment Archetypes for Cloud Applications" In this age of an interconnected world, One Network helps customers to simplify deployment of their products and services by providing a unified service and policy oriented network architecture that breaks down the boundaries of public and private clouds, different runtimes and… 13:35 Ballroom A Session Architecture Renovate to Innovate: Fundamentals of Transforming Legacy Architecture Rashmi Venugopal Product Engineering @Netflix, Speaker, Previously Product Engineer @Uber & @Microsoft, Building and Operating Reliable Distributed Systems at Scale Renovating old buildings and homes is commonplace, but why is technological renovation often overlooked? Just like a big home renovation adds to the quality of life, a successful architectural renovation has an outsized impact on the pace of innovation. 14:45 Ballroom A Session Architecture Slack's Migration to a Cellular Architecture Cooper Bethea Formerly Senior Staff Engineer and Technical Lead @Slack, Previously SRE Lead and SRE Workbook Author @Google Cellular service architectures are a conceptually simple way for highly available online services to limit the impact of cascading failures and improve scale-out. So why aren't we all using them? And how do they even work in practice? 15:55 Ballroom A Session Legacy Code Building Tomorrow’s Legacy Code, Today Shawna Martell Principal Software Engineer @Imprint, Previously @Carta, @Yahoo, @Verizon, and @Wolfram Confronting legacy code and managing technical debt are inevitable aspects of building sustainable systems. Often, when we’re building new code, we don’t keep that inevitable future in mind–that the code we’re building today is the legacy code of tomorrow.