Are there any fees for queued Google App Engine HTTP calls to the same app

The Google App Engine documentation says that after the tasks have been added to the Push Queue, the Push Queue will initiate HTTP calls to the handler / url specified in the newly added task.

My question is , are there any HTTP call charges or any other charges for internal HTTP calls initiated by Push Queue (HTTP calls that never leave GAE)?

The code for creating my task (in {root} .activities.service) looks something like this:

Queue taskQueue = QueueFactory.getQueue(QUEUENAME);
add(TaskOptions.Builder.withUrl("/activity").
     param("actor", Long.toString(activityDTO.getActor())).
     param("actorGroup", Long.toString(activityDTO.getActorGroup())).
     param("action", activityDTO.getAction()).
     param("object", activityDTO.getObject()).
     param("objectGroup", Long.toString(activityDTO.getObjectGroup())).
     method(TaskOptions.Method.GET)
);

      

The receiving endpoint in the controller (at {root} .activities.controller) looks like this:

@RestController
@RequestMapping("/activity")
public class ActivityController {
     .
     .
     .
  @RequestMapping(method = RequestMethod.GET)
  public ResponseEntity<GenericHTTPResponseDTO> recordActivity(ActivityDTO activityDTO) {

      activityService.recordActivity(activityDTO);

      return new ResponseEntity<>(HttpStatus.OK);
  }
}

      

After the Task is added to the Push-Queue, the Push-queue will then make an HTTP call to the '/ activity' endpoint, which will call the recordActivity () method.

+3


source to share


1 answer


Push Task queue requests are exposed like any other request: if you have a large number of requests, the AppEngine will increase the number of instances and you will pay more.

BUT, according to AppEngine documentation, data stored in task queues (i.e. request payload, etc.) is also stored: $ 0.026 / GB / month (2017-03 -29).



Source: https://cloud.google.com/appengine/pricing (Other Resources section)

+1


source







All Articles