TechPrufer
Get started
Atlassian
Atlassian logoAtlassian · Feature trail

Envoy Proxy Migration for Bitbucket Cloud

3 posts · Jun 2020 – Feb 2025

What this trail covers

Bitbucket Cloud has successfully migrated its public-facing edge load balancing and proxy solution to Envoy Proxy. This migration addresses previous limitations in auto-scaling and regional constraints, leading to improved reliability, cost efficiency, and performance. The new architecture leverages Envoy's extensible platform for high performance and scalability. Self-hosted Varnish Cache has been introduced for content caching, and complex routing logic has been translated into Envoy and Varnish configurations. The migration also included support for SSH and IPv6 traffic, and a phased rollout strategy to ensure zero downtime.

All Atlassian trails
  1. How we migrated Bitbucket Cloud to Envoy proxyThis post details the migration of Bitbucket Cloud's edge load balancing and proxy solution from a previous single-region, non-auto-scaling system to Envoy Proxy. Key technical contributions include: introduction of self-hosted Varnish Cache for HTTP traffic caching, translation of thousands of lines of Perl-based routing logic into Envoy and Varnish configurations, implementation of global rate limiting with per-tenant policies via Envoy contributions, addition of SSH and IPv6 support through Envoy's TCP proxying and IPv6 termination capabilities, and a phased migration strategy using weighted DNS records and dogfooding with Atlassian-originated traffic. Performance gains include reduced latency for non-US-based clients and elastic scalability.
  2. How Atlassian made Git push over HTTPS faster for Bitbucket CloudThis post details the investigation and fix for slow HTTPS Git push speeds in Bitbucket Cloud. The issue was traced to unoptimized default HTTP/2 connection buffer and frame size settings on the edge load balancers. The fix involved updating these settings to increase the max frame size, preferred frame size, and stream buffer size, which improved flow control and the receive window size. This resulted in significant speed increases for large repository pushes, particularly for users with higher latency.
  3. Zero time deployment process for Magento2This post details the use of Envoyer, a PHP deployment tool, for automating zero-downtime deployments of Magento 2 applications. It explains Envoyer's mechanism of deploying to a 'releases' directory and using symlinks for the 'current' directory. The post also covers connecting Bitbucket repositories, setting up servers with SSH keys, and customizing deployment hooks for Magento 2 specific tasks like running composer dependencies, compiling DI, deploying static content, and upgrading the database. It highlights the importance of shared files like env.php and config.php and provides examples of deployment hooks for activating new releases.