Apa yang dimaksud dengan Adaptor Apigee untuk Envoy?
Adaptor Apigee untuk Envoy adalah gateway API yang dikelola Apigee yang menggunakan
Envoy untuk melakukan proxy traffic
API. Envoy adalah proxy layanan dan edge open source populer yang dirancang untuk aplikasi native cloud. Anda dapat menjalankan Adaptor Apigee untuk Envoy di infrastruktur lokal atau di lingkungan multi-cloud.
Dengan Adaptor Apigee untuk Envoy, Anda mendapatkan aplikasi gateway API dengan jejak yang relatif kecil
yang berjalan dekat dengan aplikasi backend Anda. Adaptor Apigee untuk Envoy mengandalkan Apigee untuk:
Autentikasi dan otorisasi API (dengan kunci API dan OAuth)
Manajemen kuota
Analisis API
Tonton video:
Video ini menawarkan ringkasan dan demo Adaptor Apigee Google Cloud untuk Envoy.
Video ini menjelaskan penggunaan Adaptor Apigee untuk Envoy dengan Service Mesh.
Opsi penginstalan
Anda dapat menggunakan Adaptor Apigee untuk Envoy dalam konteks berikut:
Gambar berikut menunjukkan arsitektur tingkat tinggi untuk Adaptor Apigee untuk Envoy.
Arsitektur ini terdiri dari komponen platform pengelolaan yang di-deploy di Google Cloud Platform dan komponen platform data yang berjalan dari jarak jauh di infrastruktur lokal atau di lingkungan penyedia cloud. Bidang data mencakup proxy Envoy dan Layanan Jarak Jauh Apigee. Peran setiap komponen dijelaskan berdasarkan gambar.
Aplikasi konsumen atau klien mengakses endpoint API yang ditampilkan oleh proxy Envoy.
Proxy Envoy meneruskan konteks keamanan (menggunakan header HTTP) ke Layanan Jauh
Apigee. Layanan Jarak Jauh Apigee bertindak sebagai titik keputusan kebijakan (PDP) dan menyarankan Envoy untuk mengizinkan atau menolak akses ke konsumen API untuk permintaan tersebut.
Jika panggilan diizinkan, proxy Envoy akan meneruskan permintaan ke backend.
Layanan Jarak Jauh Apigee secara asinkron melakukan polling pada platform pengelolaan dan mendownload proxy, produk API, dan
konfigurasi lainnya yang diperlukan untuk beroperasi.
Mengapa menggunakan Adaptor Apigee untuk Envoy?
Memindahkan komponen pengelolaan API ke dekat aplikasi target backend dapat mengurangi latensi jaringan. Meskipun Anda dapat menginstal Apigee di lokasi Anda sendiri di cloud pribadi, deployment lengkap
Apigee harus besar dan kompleks untuk mendukung kumpulan fitur lengkap dan fitur yang memerlukan banyak data
seperti pengelolaan kunci, monetisasi, dan analisis. Artinya, men-deploy Apigee
di setiap pusat data tidak selalu diinginkan.
Manfaat menggunakan Adaptor Apigee untuk Envoy meliputi:
Mengurangi latensi traffic API untuk layanan yang berjalan dalam jarak dekat.
Penggunaan rangkaian lengkap metrik, dasbor, dan API Apigee Analytics.
Mempertahankan traffic API dalam batas yang disetujui perusahaan untuk tujuan keamanan atau kepatuhan.
Komunikasi asinkron dengan Apigee memungkinkan data traffic API diambil dan
dikirim ke Apigee tanpa memengaruhi latensi.
Adaptor dapat mentoleransi gangguan komunikasi sementara dengan bidang manajemen. Namun, seiring waktu, gangguan dapat menyebabkan hilangnya fungsi. Adaptor memerlukan
komunikasi dengan bidang pengelolaan untuk:
Membuat token OAuth
Memverifikasi kunci API (koneksi diperlukan untuk verifikasi pertama, setelah itu akan di-cache)
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eApigee Adapter for Envoy is an Apigee-managed API gateway that uses Envoy to proxy API traffic, suitable for on-premises or multi-cloud environments.\u003c/p\u003e\n"],["\u003cp\u003eThis adapter provides API authentication, authorization, and quota management, relying on Apigee for these core functionalities.\u003c/p\u003e\n"],["\u003cp\u003eIt can be deployed as a native service or within an Istio service mesh integrated with Apigee hybrid, offering flexibility in deployment.\u003c/p\u003e\n"],["\u003cp\u003eUsing Apigee Adapter for Envoy reduces API traffic latency by situating API management closer to backend applications, with benefits such as full access to Apigee Analytics.\u003c/p\u003e\n"],["\u003cp\u003eThe adapter communicates asynchronously with the Apigee management plane for various functions like OAuth token generation and quota enforcement, while being able to tolerate temporary communication interruptions.\u003c/p\u003e\n"]]],[],null,["# Apigee Adapter for Envoy overview\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nWhat is Apigee Adapter for Envoy?\n---------------------------------\n\n\nApigee Adapter for Envoy is an Apigee-managed API gateway that uses\n[Envoy](https://www.envoyproxy.io/docs/envoy/latest/intro/what_is_envoy) to proxy API\ntraffic. Envoy is a popular, open source edge and service proxy designed for cloud-native\napplications. You can run Apigee Adapter for Envoy on premises or in a multi-cloud environment.\n\nWith Apigee Adapter for Envoy, you get a relatively small footprint API gateway application\nrunning close to your backend applications. Apigee Adapter for Envoy relies on Apigee for:\n\n- API authentication and authorization (with API keys and OAuth)\n- Quota management\n- API analytics\n\n\n**Watch videos:** \nThis video offers an overview and demo of Google Cloud's Apigee Adapter for Envoy. \nThis video describes using the Apigee Adapter for Envoy with Service Mesh.\n\nInstallation options\n--------------------\n\n\nYou can use the Apigee Adapter for Envoy in the following context:\n\n- As a native service. See [Native Envoy example for Apigee and hybrid](/apigee/docs/api-platform/envoy-adapter/v2.0.x/example-apigee).\n- As a service deployed to the Istio service mesh integrated with Apigee hybrid. See [Apigee hybrid example with Kubernetes](/apigee/docs/api-platform/envoy-adapter/v2.0.x/example-hybrid).\n\nApigee Adapter for Envoy\n------------------------\n\n\nThe following figure shows the high level architecture for Apigee Adapter for Envoy.\nThis architecture consists of management plane components deployed on Google Cloud Platform\nand data plane components running remotely on premises or in a cloud provider environment. The\ndata plane includes the Envoy proxy and Apigee Remote Service. The role of each component\nis described following the figure.\n\n1. A consumer or client app accesses an API endpoint exposed by the Envoy proxy.\n2. The Envoy proxy passes the security context (using HTTP headers) to the Apigee Remote Service. The Apigee Remote Service acts as a policy decision point (PDP) and advises Envoy to allow or deny access to the API consumer for the request.\n3. If the call is allowed, the Envoy proxy forwards the request to the backend.\n4. The Apigee Remote Service asynchronously polls the management plane and downloads proxy, API product, and other configuration that it needs to operate.\n\nWhy use Apigee Adapter for Envoy?\n---------------------------------\n\nMoving the API management component close to backend target applications can reduce network\nlatency. While you can install Apigee on-premises in a private cloud, a full deployment of\nApigee is necessarily large and complex to support its full feature-set and data-heavy\nfeatures like key management, monetization, and analytics. This means that deploying Apigee\non premises in each data-center is not always desirable.\n\nBenefits of using Apigee Adapter for Envoy include:\n\n- Reduced latency of API traffic for services that run in close proximity.\n\n- Use of the full suite of Apigee Analytics metrics, dashboards, and APIs.\n- Keeps API traffic within the enterprise-approved boundaries for security or compliance purposes.\n- Asynchronous communication with Apigee allows API traffic data to be captured and sent to Apigee without affecting latency.\n- The adapter can tolerate temporary communication interruptions with the management plane. Over time, however, an interruption can lead to loss of functionality. The adapter requires communication with the management plane for:\n - Generating OAuth tokens\n - Verifying API keys (connection is required for the first verification, after which it is cached)\n - Enforcing quotas\n - Sending analytics data to the management plane\n\nNext step\n---------\n\n[Install Apigee Adapter for Envoy](/apigee/docs/api-platform/envoy-adapter/v2.0.x/getting-started)"]]
