• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Serverless Applications with Node.js: About Claudia API Gateway

Ranch Hand
Posts: 108
Netbeans IDE Firefox Browser Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Slobodan Stojanovic and Aleksandar Simovic,

Node.js used Claudia API Gateways between a browser request and AWS Lambda functions. It also discussed various services and routines to route event handlers.

In asynchronous form, it works as like AJAX XMLHttpRequest service used in JavaScript.
As a note, XMLHttpRequest can also be sent/received either synchronous or asynhronous manner. Have a at code as below.

Similiarly, used to get server response as stream.
Here I want to ask, Is it working for similiar functionaly as provided by JavaScript services using XMLHttpRequest functions?

Thank you
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Claudia API Builder is just a Node module that does simple routing and few other necessary things, but the layer between browser and your Lambda function is Amazon API Gateway. It listens to HTTP requests and then triggers your AWS Lambda function synchronously (it waits for the reply). But it also does much more, for example, auto-scaling, security, authorization, etc.

It's not like AJAX XMLHttpRequest, as that one is used to invoke HTTP request asynchronously on the front end side. API Gateway is on the backend, and it invokes your Lambda function synchronously.

Second chapter of our book talks a bit more about API Gateway integration.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic