Google Cloud의 일부 대규모 서비스와 동일한 기본 인프라를 기반으로 구축된 애플리케이션 통합은 자동 확장 기능을 제공합니다. 자동 확장을 사용하면 통합 워크로드가 변화하는 수요에 자동으로 적응할 수 있습니다. 이를 통해 대부분의 경우 수동 개입이나 복잡한 조정이 필요하지 않으며 안정적인 성능과 원활한 확장이 가능합니다.
Application Integration 확장 방식
Application Integration은 수평 및 수직 확장을 모두 사용하여 다양한 워크로드를 관리합니다.
수평 확장
워크로드 또는 수요에 따라 Application Integration 인스턴스를 프로비저닝하거나 프로비저닝 해제하여 동적으로 확장합니다. 수요가 증가하면 수평 자동 확장은 동시에 실행되고 증가한 부하를 처리할 추가 인스턴스를 프로비저닝합니다. 반대로 활동이 적은 기간에는 리소스 사용량을 최적화하기 위해 사용되지 않는 인스턴스가 프로비저닝 해제됩니다.
예: 주문 수가 급증하면 자동 확장이 트리거되어 증가한 양을 처리하고 요청을 동시에 처리하기 위해 추가 통합 인스턴스가 프로비저닝됩니다.
수직 확장
필요에 따라 각 개별 작업 또는 애플리케이션 통합 인스턴스에 추가 리소스 (예: GCU 및 RAM)를 할당하여 확장합니다. 세로 확장은 인스턴스를 더 프로비저닝하는 대신 기존 인스턴스의 성능을 개선합니다.
예: 복잡한 데이터 변환 작업에는 추가 메모리가 필요할 수 있습니다. 수직 확장은 태스크를 더 효율적으로 완료하는 데 도움이 되도록 추가 메모리를 할당합니다.
Application Integration은 정의된 할당량 및 한도를 준수하며 요청 시 이를 늘릴 수 있습니다. 자세한 내용은 할당량 및 한도를 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[],[],null,["# About autoscaling in Application Integration\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nAbout autoscaling in Application Integration\n============================================\n\nApplication Integration, built on the same underlying infrastructure as some of Google Cloud's largest-scale services, offers autoscaling capabilities. Autoscaling enables integration workloads to adapt automatically to changing demands. This helps eliminate the need for manual intervention or complex tuning in most cases and provides reliable performance and seamless scaling.\n\nHow Application Integration scales\n----------------------------------\n\nApplication Integration uses both horizontal and vertical scaling to manage varying workloads:\n\n### Horizontal scaling\n\nScales out dynamically by provisioning or deprovisioning the Application Integration instances based on the workload or demand. When demand increases, horizontal autoscaling provisions additional instances to run concurrently and handle the increased load. Conversely, during periods of low activity, the unused instances are deprovisioned to optimize resource usage.\n\n**Example:** A sudden surge in orders can trigger autoscaling, which provisions additional integration instances to handle the increased volume and process requests in parallel.\n\n### Vertical scaling\n\nScales up by allocating additional resources (such as GCU and RAM) to each individual task or Application Integration instance on demand. Instead of provisioning more instances, vertical scaling enhances the performance of the existing instances.\n\n**Example:** A complex data transformation task may require additional memory. Vertical scaling allocates additional memory to help complete the task more efficiently.\n| **Note:** The Application Integration platform automatically provisions additional resources as needed during scaling. This dynamic provisioning may introduce brief latency while the resources are being initialized. To ensure smooth and reliable performance during anticipated traffic surges (such as marketing campaigns or seasonal peaks), it's recommended to plan ahead and request resource scaling in advance. If you require assistance with proactive scaling, [contact support](/application-integration/docs/getting-support).\n\nApplication Integration adheres to defined quotas and limits, which can be increased upon request. For more information, see [Quotas and limits](/application-integration/docs/quotas).\n\nTo understand the autoscaling behavior of Integration Connectors, see [About autoscaling in Integration Connectors](/integration-connectors/docs/autoscaling).\n\nBenefits\n--------\n\nThe autoscaling features of Application Integration provide the following advantages:\n\n- **Performance at scale:** Automatically adjust to changes in traffic and usage. Planned scaling is still recommended for predictable, high-impact events like seasonal peaks.\n- **Reduced operational overhead:** Scaling is automated and doesn't require manual intervention in most cases. For extreme load spikes, advance planning may still be needed.\n- **Enhanced reliability:** Responds to traffic spikes while maintaining service availability.\n- **Simplified management:** Scaling is handled by Google Cloud's infrastructure, letting teams focus on building integrations instead of managing scaling infrastructure.\n\nObservability and monitoring\n----------------------------\n\nApplication Integration automatically exports a rich set of metrics to Cloud Monitoring, providing deep insights into the usage, performance, and health of your integrations.\n\nWhile a single, pre-built dashboard for all metrics across projects isn't directly available within the Application Integration platform, you can leverage Cloud Monitoring to create custom dashboards tailored to your specific needs.\n\n### Key Application Integration metrics\n\nFor a comprehensive list of all Application Integration metrics available for monitoring, refer to [Monitor Application Integration resources](/application-integration/docs/monitoring-overview)."]]
