Make Secure Online Meeting Platform

“After adopting APISIX Ingress Controller, it is easier for developers to add configurations on the gateway than to write codes.”

Zoom

> 100 backend services

are manage unifiedly with ease

Unify middleware worldwide

into a continuous delivery pipeline

Start for Free

Challenge

Like other SaaS and internet companies, Zoom has encountered technical challenges as its business rapidly expands.

  • A significant number of microservices: Due to Zoom’s rapid growth of business and teams, over 100 backend services need to be delivered. However, it is hard to manage a large number of microservices efficiently.

  • Various deployment environments: Zoom’s business services are all over the world, so there are technical challenges with a large number of hybrid cloud environments.

  • Complex infrastructure: As Zoom’s managing R&D teams are distributed globally, it is a great challenge to integrate these complex middleware and infrastructure into the continuous delivery pipeline.

The above challenges are not a simple additive relationship but a multiplicative relationship. In other words, the actual situation is far more complex.

Solution

Zoom decides to make its continuous delivery pipeline to solve those pain points. Considering data security and service stability, Zoom chose APISIX Ingress Controller and migrates the configurations of hundreds of API gateways to APISIX, thus implementing its continuous delivery pipeline.

Competitive Edge of Our Solution

Taking its business scenarios into consideration, Zoom attached more emphasis to the two parts, which can be satisfied by APISIX Ingress Controller.

Data Security

Zoom takes customer privacy and service security seriously; thus, mTLS authentication and verification are widely used in online meeting rooms and phone calls. Nevertheless, many similar API gateways can only provide such a service in their enterprise version, while APISIX Ingress provides great feasibility and convenience to achieve this goal.

Service Stability

Zoom’s backend services require Multi-AZ (Multi-Availability Zones) deployments for high availability across different regions. Generally, it puts businesses in other DC. If an error occurs in the original DC, the client traffic needs to be transferred to another one, in which APISIX Ingress can successfully meet the requirement.

Results

Project Management

Zoom uses a GitOps workflow internally to build API Gateway configuration into the application delivery model. Under this model, the definition of APISIX routing rules is integrated with “Deploy” and other links, handing over the change control to GitHub. With the creation and merging of GitHub branches, the pipeline realizes consistent timelines between application and gateway configuration release and rollback.

Application Development

Developers focus on APIs’ routing and authentication capabilities, and developing and implementing business functions and the upper-level business, hoping to build an out-of-the-box infrastructure. Integrating APISIX’s configuration and the continuous delivery pipeline workflow provides developers with a more labor-saving way.

Environment Management

Some configurations of APISIX ingress were implemented to meet the requirement of reducing environmental differences. Therefore, system managers can comprehensively control the differences in some heterogeneous environments. Zoom can use customized configuration to disable tracing for some environments, convert ApisixRoute objects to native Ingress objects and NGINX Ingress Annotation, and use different images to pull secrets.

Infrastructure Management

Each plugin of the pipeline provides configuration items for infrastructure engineers. After the API gateway team configures the property, the setting will take effect on all the services, which are suitable for a unified security and risk control strategy.

API7.ai Logo

API Management for Modern Architectures with Edge, API Gateway, Kubernetes, and Service Mesh.

Product

Documentation

SOC2 Type IRed Herring

Copyright © HONG KONG APISEVEN LIMITED. 2019 – 2023. Apache, Apache APISIX, APISIX, and associated open source project names are trademarks of the Apache Software Foundation