diff --git a/docs/components/best-practices/development/writing-good-workers.md b/docs/components/best-practices/development/writing-good-workers.md index 1adbcc3d3d..b47389515a 100644 --- a/docs/components/best-practices/development/writing-good-workers.md +++ b/docs/components/best-practices/development/writing-good-workers.md @@ -242,12 +242,12 @@ These observations yield the following recommendations: ### Node.js client -Using the [Node.js client](https://github.com/camunda/camunda-platform-get-started/tree/master/nodejs), your worker code will look like this, assuming that you use Axios to do rest calls (but of course any other library is fine as well): +Using the [Node.js client](https://github.com/camunda/camunda-8-js-sdk), your worker code will look like this, assuming that you use Axios to do rest calls (but of course any other library is fine as well): ```js zbc.createWorker({ taskType: "rest", - taskHandler: (job, _, worker) => { + taskHandler: (job) => { console.log("Invoke REST call..."); axios .get(PAYMENT_URL) @@ -266,7 +266,7 @@ zbc.createWorker({ This is **reactive code**. And a really interesting observation is that reactive programming is so deep in the JavaScript language that it is impossible to write blocking code, even code that looks blocking is still [executed in a non-blocking fashion](https://github.com/berndruecker/camunda-cloud-clients-parallel-job-execution/blob/main/results/nodejs-blocking.log). -Node.js code scales pretty well and there is no specific thread pool defined or necessary. The Camunda 8 Node.js client library also [uses reactive programming internally](https://github.com/camunda-community-hub/zeebe-client-node-js/blob/master/src/zb/ZBWorker.ts#L28). +Node.js code scales pretty well and there is no specific thread pool defined or necessary. The Camunda 8 Node.js client library also [uses reactive programming internally](https://github.com/camunda/camunda-8-js-sdk/blob/main/src/zeebe/zb/ZBWorker.ts#L27). This makes the recommendation very straight-forward: