An overview of different ways to schedule REST API calls with IBM Cloud offerings.

IBM Workload Scheduler on IBM Cloud was deprecated in March of 2019, and some people worried that scenarios in which that service was used—in particular, scheduling REST API calls—would no longer be covered by IBM Cloud service offerings.

Fortunately, if you need to schedule a REST API call periodically (just to see the output without any post-process), you can still use IBM Cloud Kubernetes Service, Cloud Foundry on IBM Cloud, or IBM Cloud Functions. This post will outline how to use the different offerings.

CronJob in IBM Cloud Kubernetes Service

Kubernetes allows you to define a scheduled periodic job using a pre-defined controller: <a data-entity-substitution="" data-entity-type="" data-entity-uuid="" href="https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/" target="_blank">CronJob</a>.

CronJobs work like Cron in Unix systems and are very simple to setup. Please see the example below:

apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: hello
spec:
  schedule: "*/1 * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: getFoo
            image: busybox
            args:
            - /bin/sh
            - -c
            - curl -X GET http://www.example.com/bar/foo
          restartPolicy: OnFailure

In this example, we define a REST API call to http://www.example.com/bar/foo each minute.

CronJobs in Cloud Foundry

Cloud Foundry is not generally used to run periodic jobs, so there is no native solution to schedule REST API calls. However, you could define a silly application in whatever programming language you prefer to run this periodic job.

For example, using Node.js as runtime:

const request = require(‘request’);

const doTheRequest = () => {
    request({
        uri: "http://www.example.com/bar/foo",
	 method: "GET"	
    }, function (error, response, body) {
        console.log('response', body); 
    });

setInterval(doTheRequest, 60000);

This approach for periodic jobs would be useful in some cases (e.g., tests), but it is not recommended. The application could face some issues due to the health check Cloud Foundry performs for each app.

To adopt this approach, it would be useful to disable health check during the application push phase by using the following command: 

ibmcloud cf push <APPNAME> -u process --no-route

Periodic Actions in IBM Cloud Functions

The serverless computing approach allows for an easy way to create periodic jobs. With IBM Cloud Functions (based on the open source project Apache OpenWhisk), it is possible to create Actions (stateless code snippets) configured to execute a specific task, which can be triggered/invoked periodically.

For example, you could define an Action using Node.js as runtime with the following code:

/**
  *
  * main() will be run when you invoke this action
  *
  * @param Cloud Functions actions accept a single parameter, which must be a JSON object.
  *
  * @return The output of this action, which must be a JSON object.
  *
  */
function main(params) {
    const request = require(‘request’);
    request({
        uri: "http://www.example.com/bar/foo",
	 method: "GET"	
    }, function (error, response, body) {
        console.log('response', body);
        return { message: body };
    });
}

Once the Action is created, you could transform it into a periodic job linking it to a “Periodic” type Trigger.

Summary

These are a few short examples that illustrate how to schedule REST API calls with different offerings in IBM Cloud.

The right approach depends on your knowledge and how complex the post-processing may be. As you can see, the serverless approach is the simplest one, and you can test it yourself by following the steps described here.

If you are looking for a more customized approach, try using CronJobs in the manner described here.

Was this article helpful?
YesNo

More from Cloud

The history of the central processing unit (CPU)

10 min read - The central processing unit (CPU) is the computer’s brain. It handles the assignment and processing of tasks, in addition to functions that make a computer run. There’s no way to overstate the importance of the CPU to computing. Virtually all computer systems contain, at the least, some type of basic CPU. Regardless of whether they’re used in personal computers (PCs), laptops, tablets, smartphones or even in supercomputers whose output is so strong it must be measured in floating-point operations per…

A clear path to value: Overcome challenges on your FinOps journey 

3 min read - In recent years, cloud adoption services have accelerated, with companies increasingly moving from traditional on-premises hosting to public cloud solutions. However, the rise of hybrid and multi-cloud patterns has led to challenges in optimizing value and controlling cloud expenditure, resulting in a shift from capital to operational expenses.   According to a Gartner report, cloud operational expenses are expected to surpass traditional IT spending, reflecting the ongoing transformation in expenditure patterns by 2025. FinOps is an evolving cloud financial management discipline…

IBM Power8 end of service: What are my options?

3 min read - IBM Power8® generation of IBM Power Systems was introduced ten years ago and it is now time to retire that generation. The end-of-service (EoS) support for the entire IBM Power8 server line is scheduled for this year, commencing in March 2024 and concluding in October 2024. EoS dates vary by model: 31 March 2024: maintenance expires for Power Systems S812LC, S822, S822L, 822LC, 824 and 824L. 31 May 2024: maintenance expires for Power Systems S812L, S814 and 822LC. 31 October…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters