Skip to content

Commit e189186

Browse files
KarlEricksonKarlErickson
committed
updates per feedback
1 parent b9a1b2f commit e189186

File tree

2 files changed

+8
-12
lines changed

2 files changed

+8
-12
lines changed

‎articles/spring-apps/cost-management.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -26,10 +26,6 @@ The first 50 vCPU hours and 100-GB hours of memory are free each month. For more
2626

2727
If you have Azure Spring Apps instances that don't need to run continuously, you can save costs by reducing the number of running instances. For more information, see [Start or stop your Azure Spring Apps service instance](how-to-start-stop-service.md).
2828

29-
## Standard consumption and dedicated plan
30-
31-
Unlike other pricing plans, the Standard consumption and dedicated plan offers a pure consumption-based pricing model. You can dynamically add and remove resources based on the resource utilization, number of incoming HTTP requests, or by events. When running apps in a consumption workload profile, you're charged for active and idle usage of resources, and the number of requests. For more information, see the [Standard consumption and dedicated plan](overview.md#standard-consumption-and-dedicated-plan) section of [What is Azure Spring Apps?](overview.md)
32-
3329
## Scale and autoscale
3430

3531
You can manually scale computing capacities to accommodate a changing environment. For more information, see [Scale an application in Azure Spring Apps](how-to-scale-manual.md).
@@ -38,27 +34,27 @@ Autoscale reduces operating costs by terminating redundant resources when they'r
3834

3935
You can also set up autoscale rules for your applications in the Azure Spring Apps Standard consumption and dedicated plan. For more information, see [Quickstart: Set up autoscale for applications in the Azure Spring Apps Standard consumption and dedicated plan](quickstart-apps-autoscale-standard-consumption.md).
4036

41-
## Stop maintaining unused environments
37+
## Stop maintaining unused environments
4238

4339
If you set up several environments while developing a product, it's important to remove the environments that are no longer in use once the product is live.
4440

45-
## Remove unnecessary deployments
41+
## Remove unnecessary deployments
4642

4743
If you use strategies like blue-green deployment to reduce downtime, it can result in many idle deployments on staging slots, especially multiple app instances that aren't needed once newer versions are deployed to production.
4844

49-
## Avoid over allocating resources
45+
## Avoid over allocating resources
5046

5147
Java users often reserve more processing power and memory than they really need. While it's fine to use large app instances during the initial months in production, you should adjust resource allocation based on usage data.
5248

53-
## Avoid unnecessary scaling
49+
## Avoid unnecessary scaling
5450

5551
If you use more app instances than you need, you should adjust the number of instances based on real usage data.
5652

57-
## Streamline monitoring data collection
53+
## Streamline monitoring data collection
5854

5955
If you collect more logs, metrics, and traces than you can use or afford, you must determine what's necessary for troubleshooting, capacity planning, and monitoring production. For example, you can reduce the frequency of application performance monitoring or be more selective about which logs, metrics, and traces you send to data aggregation tools.
6056

61-
## Deactivate debug mode
57+
## Deactivate debug mode
6258

6359
If you forget to switch off debug mode for apps, a large amount of data is collected and sent to monitoring platforms. Forgetting to deactivate debug mode could be unnecessary and costly.
6460

‎articles/spring-apps/plan-comparison.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: devx-track-java, devx-track-extended-java, devx-track-azurecli, event
1616
1717
This article provides a comparison of plans available in Azure Spring Apps. Each plan is designed to cater to different customer scenarios and purposes, as described in the following list:
1818

19-
- Enterprise plan: This plan is designed to expedite the development and deployment of mission-critical and large-scale enterprise applications with higher SLA and large microservice cluster support. This plan also addresses enterprise requirements around configuration management, service discovery, API gateway, API portal, ease of integration, portability, and flexibility with on-demand managed Tanzu commercial components and Tanzu Spring Runtime support, built on top of strong partnership between VMware and Microsoft.
19+
- Enterprise plan: This plan is designed to expedite the development and deployment of mission-critical and large-scale enterprise applications with higher SLA and large application cluster support. This plan also addresses enterprise requirements around configuration management, service discovery, API gateway, API portal, ease of integration, portability, and flexibility with on-demand managed Tanzu commercial components and Tanzu Spring Runtime support, built on top of strong partnership between VMware and Microsoft.
2020
- Basic plan: An entry-level plan for individual development and testing.
2121
- Standard plan: A Spring-centric and opinionated application hosting platform with built-in and pre-configured settings for build, service registry, storage, and more.
2222
- Standard consumption and dedicated plan: This plan is hosted in an Azure Container Apps environment and is designed to seamlessly interact with other apps running in the same environment with simplified networking and unified observability.
@@ -41,7 +41,7 @@ The following table shows the differences between each plan:
4141
| PHP app support | Build and deploy PHP apps. | ✔️ | ❌ | ❌ | ❌ |
4242
| Static web app support | Build and deploy static web apps with static web content, like CSS, JS, and HTML files. | ✔️ | ❌ | ❌ | ❌ |
4343
| Zero downtime deployment | Rolling update and blue/green deployment strategies with assured zero downtime and affect for apps. | ✔️ | ✔️ | ✔️ | ✔️ |
44-
| Custom domain | Support multiple custom domains on apps. | ✔️ | ✔️ | ✔️ | ✔️ |
44+
| Custom domain | Support multiple custom domains on apps. | ✔️ | ❌ | ✔️ | ✔️ |
4545
| Bring your own storage | Support to mount Azure storage for apps to use. | ✔️ | ✔️ | ✔️ | ✔️ |
4646
| Custom health probes | Support to customize apps on health probes, like liveness, readiness, and startup probes, and graceful termination periods. | ✔️ | ✔️ | ✔️ | ✔️ |
4747
| Auto patching | Automatic patching of the base OS, language runtime (such as the JDK), and APM agents in maintaining images for apps. | ✔️ | ✔️ | ✔️ | ✔️ |

0 commit comments

Comments
 (0)