You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/overview-webjobs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,15 +59,15 @@ WebJobs also provide **built-in logging** via Kudu and integration with App Serv
59
59
60
60
## Scaling considerations
61
61
62
-
WebJobs scale together with your App Service plan. If your app is configured to scale out to multiple instances, your WebJobs will run on each instance as appropriate:
62
+
WebJobs scale together with your App Service plan. If your app is configured to scale out to multiple instances, your WebJobs run on each instance as appropriate:
63
63
-**Triggered WebJobs** will run on a single instance by default.
64
64
-**Continuous WebJobs** can be configured to run on all instances or a single one using the `WEBJOBS_RUN_ONCE` setting.
65
65
66
66
If you need independently scalable or event-driven execution, [Azure Functions](../azure-functions/functions-overview.md) may be more appropriate.
67
67
68
68
## Best practices
69
69
70
-
- Use **triggered** WebJobs for ad hoc or scheduled operations.
70
+
- Use **triggered** WebJobs for improvised or scheduled operations.
71
71
- Use **continuous** WebJobs only when the task needs to run constantly (e.g., polling a queue).
72
72
- Implement **retry logic and error handling** within your scripts.
73
73
- Use **application logging** and **Kudu logs** to monitor job behavior.
@@ -85,8 +85,8 @@ If you need independently scalable or event-driven execution, [Azure Functions](
85
85
86
86
## <aname="NextSteps"></a> Next steps
87
87
88
-
-[Background jobs best practices – Azure Architecture Center](/azure/architecture/best-practices/background-jobs)
88
+
-[Review background jobs best practices – Azure Architecture Center](/azure/architecture/best-practices/background-jobs)
89
89
-[Develop WebJobs using Visual Studio](webjobs-dotnet-deploy-vs.md)
90
90
-[Get started with the WebJobs SDK](webjobs-sdk-get-started.md)
91
91
-[Use the WebJobs SDK to build advanced jobs](webjobs-sdk-how-to.md)
92
-
-[Kudu WebJobs reference on GitHub](https://github.com/projectkudu/kudu/wiki/WebJobs)
92
+
-[Review Kudu WebJobs reference on GitHub](https://github.com/projectkudu/kudu/wiki/WebJobs)
Copy file name to clipboardExpand all lines: articles/app-service/tutorial-webjobs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -271,13 +271,13 @@ public class HelloWorld {
271
271
272
272
### Build the Java WebJob
273
273
274
-
1. The `run.sh` script runs a jar with the name that's setin the Maven configuration. This script will run when our WebJob is triggered.
274
+
1. The `run.sh` script runs a jar with the name that sets in the Maven configuration. This script runs when our WebJob is triggered.
275
275
276
276
```bash
277
277
java -jar webjob-artifact-1.0.0.jar
278
278
```
279
279
280
-
1. Next, we compile the Java project to produce the executable `.jar`. There are multiple ways to do this, but for this example, we’ll use Maven. Run the following commands from the `project/` directory:
280
+
1. Next, we compile the Java project to produce the executable `.jar`. There are multiple ways to do this, but for this example, we use Maven. Run the following commands from the `project/` directory:
281
281
282
282
```bash
283
283
mvn install
@@ -322,7 +322,7 @@ public class HelloWorld {
322
322
323
323
:::zone target="docs" pivot="php"
324
324
325
-
WebJobs is a feature of Azure App Service that enables you to run a program or script in the same instance as a web app. All app service plans support WebJobs at no additional cost. This sample uses a scheduled (Triggered) WebJob to output the system time once every minute.
325
+
WebJobs is a feature of Azure App Service that enables you to run a program or script in the same instance as a web app. All app service plans support WebJobs at no extra cost. This sample uses a scheduled (Triggered) WebJob to output the system time once every minute.
326
326
327
327
## Prerequisites
328
328
@@ -333,7 +333,7 @@ WebJobs is a feature of Azure App Service that enables you to run a program
333
333
334
334
## Download the sample WebJob
335
335
336
-
You can [download a pre-built sample project](https://github.com/Azure-Samples/App-Service-PHP-WebJobs-QuickStart/archive/refs/heads/main.zip) to get started quickly. The sample includes two files: `webjob.php` and `run.sh`.
336
+
You can [download a prebuilt sample project](https://github.com/Azure-Samples/App-Service-PHP-WebJobs-QuickStart/archive/refs/heads/main.zip) to get started quickly. The sample includes two files: `webjob.php` and `run.sh`.
337
337
338
338
The PHP script, `webjob.php`, outputs the current time to the console as shown below:
0 commit comments