Background Introduction
In some situation, customers find existing application can meet their requirements functionally. But customers have concerns about the performance. For example, we have build mission Add Printing Labels to Your User Experience for SAP S/4HANA Cloud with CAP Node.js, but customers have concerns for high concurrency situation. Then does customer need to adjust the existing code? The answer is no need. Customer can add Application Autoscaler Service Binding To Deployed Application and create Scaling Policy for the deployed application.
Steps:
Step 1. Add Application Autoscaler Service Binding To Deployed Backend Application
The following Json file defines the Scaling Policy. I will explain it a little later .
{
“instance_min_count”: 1,
“instance_max_count”: 5,
“scaling_rules”: [
{
“metric_type”: “memoryused”,
“breach_duration_secs”: 600,
“threshold”: 90,
“operator”: “>=”,
“cool_down_secs”: 300,
“adjustment”: “+1”
},
{
“metric_type”: “memoryused”,
“breach_duration_secs”: 600,
“threshold”: 30,
“operator”: “<“,
“cool_down_secs”: 300,
“adjustment”: “-1”
}
]
}
Step 2. Restart your backend application.
Step 3. You can check your scaler history in Application Autoscaler Dashboard.
Explanation for Scaling Policy
You can define a policy to scale your application instances either dynamically or based on schedule.
If you want to scale your application instances based on memory or CPU usage, response time, throughput, or custom metrics. You can use Dynamic Scaling Policy
If you want scale your application instances based on schedules, you can use Schedule-Based Scaling Policy.
The Ends!
Thanks for your time!
Jacky Liu
Background IntroductionIn some situation, customers find existing application can meet their requirements functionally. But customers have concerns about the performance. For example, we have build mission Add Printing Labels to Your User Experience for SAP S/4HANA Cloud with CAP Node.js, but customers have concerns for high concurrency situation. Then does customer need to adjust the existing code? The answer is no need. Customer can add Application Autoscaler Service Binding To Deployed Application and create Scaling Policy for the deployed application.Steps:Step 1. Add Application Autoscaler Service Binding To Deployed Backend ApplicationThe following Json file defines the Scaling Policy. I will explain it a little later .{
“instance_min_count”: 1,
“instance_max_count”: 5,
“scaling_rules”: [
{
“metric_type”: “memoryused”,
“breach_duration_secs”: 600,
“threshold”: 90,
“operator”: “>=”,
“cool_down_secs”: 300,
“adjustment”: “+1”
},
{
“metric_type”: “memoryused”,
“breach_duration_secs”: 600,
“threshold”: 30,
“operator”: “<“,
“cool_down_secs”: 300,
“adjustment”: “-1”
}
]
}Step 2. Restart your backend application.Step 3. You can check your scaler history in Application Autoscaler Dashboard.Explanation for Scaling PolicyYou can define a policy to scale your application instances either dynamically or based on schedule.If you want to scale your application instances based on memory or CPU usage, response time, throughput, or custom metrics. You can use Dynamic Scaling PolicyIf you want scale your application instances based on schedules, you can use Schedule-Based Scaling Policy. The Ends!Thanks for your time!Jacky Liu Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
