Adolfo Garza – Page 2

Getting Started with Serverless Integrations

August 12, 2018 Adolfo Garza Comments 130 comments

Serverless functions (also known as functions as a service) can help you simplify your integrations because you only need to code your logic in a function and the service provider will take care of all the backend hardware, scaling, OS, availability, instances, etc…

Other benefits of serverless technology are that the hardware and software is fully managed, scales automatically almost instantly, and you only pay whenever your function runs so it can be very inexpensive.

Some of the most popular serverless providers are Amazon Lambda, Azure Functions and Google Cloud Functions.

For this demonstration we will use Google Cloud Functions. We will integrate a Shopify Webhook with Netsuite. My code will run in NodeJS Javascript and the rest will be managed by Google. As a developer coming from a Netsuite background I found it extremely easy to get started with Google Cloud Functions.

You can set this up within minutes as explained in this video: https://youtu.be/nOlfG5oGets
Google Cloud Functions Code:

var ENDPOINT = 'https://xxxxxxx';

/**

* Responds to any HTTP request that can provide a "message" field in the body.

* @param {!Object} req Cloud Function request context.

* @param {!Object} res Cloud Function response context.

exports.run = function run(req, res) {

console.log('Receiving Request');

const https = require('https');

var url = ENDPOINT.replace('https://', '').split('/');

var options = {

host: url.shift(),

path: '/' + url.join('/'),

method: 'POST'

};

var requ = https.request(options, function (resp) {

resp.on('data', function (responseData) {

console.log('Response Data: ' + responseData);

res.status(200).send(responseData);

return;

});

var postBody = {

headers: req.headers,

query: req.query,

body: req.body

};

requ.write(JSON.stringify(postBody));

requ.end();

};

This was a quick demonstration on how to get started. From here you can expand the code and keep developing to make your function more robust.

Some suggestions on first things to do:

Secure your function by adding a password.
Add more logging and different levels of logging.
Branch out the logic depending on the data being received.
Add node plugins.
Make use of other Google Cloud Services such as Google Datastore or Google Storage.

Epic Battle: Concurrent Map Reduce vs Concurrent Suitelet

July 8, 2017 Adolfo Garza Comments 1,227 comments

Spoiler: 50 concurrent Suitelet win. (Tested in Sandbox)

I am a big fan of Map Reduce scripts, spreading the load among 5 queues makes a huge difference when processing your data. Unfortunately to take advantage of the concurrent queues feature your account must have a SuiteCloud plus license.

So I figured it would be cool to simulate this feature with Suitelets. Suitelets support up to 50 concurrent connections and they are available without the need of SuiteCloud plus.

The results were very surprising.

Test scenario:

Task: Create and delete a custom record with no fields.
Account: Account with SuiteCloud Plus license in Sandbox.
Map Reduce: Run task 10k times by returning an array of 10k elements on the getInputData step and let the reduce step handle the main logic.
Suitelet SS2.0: Run task once per call. Return “OK” as response. Available without login (External).
Use Apache JMeter to call the Suitelet 10k times.
Additionally call the Suitelet using Ajax with browser (Chrome) 5k times (to avoid browser memory issues).

1 2	var newRec = RECORDMODULE.create({type: 'customrecord_load_test' }).save(); RECORDMODULE.delete({ type: 'customrecord_load_test', id: newRec});

Here are the results:

Map Reduce w/buffer size of 1 : 196 seconds ~ 51 per second
Map Reduce w/buffer size of 64: 518 seconds ~ 19 per second
Suitelet w/JMeter w/50 at a time: 55 seconds ~ 181 per second
Suitelet w/JMeter w/100 at a time: 30 seconds ~ 333 per second
Suitelet w/JMeter w/200 at a time: 24 seconds ~ 416 per second
Suitelet w/JMeter w/250 at a time: 24 seconds ~ 416 per second
Suitelet w/JQuery: 1000/44 secs ~ 22 per second

As you can see, I ran multiple test variations. After I saw that the Suitelet was able to handle 50 requests at a time I went crazy and increased the number of concurrent requests. I got up to 250 requests being handled successfully. Once I reached 300 requests at a time I started getting errors and not all the records were successfully created.

As you can see, after 200 requests you pretty much get the same speed. This could be caused by my system, JMeter, my internet connection or by some throttling happening on the Netsuite side, I don’t know.

Conclusion:

This approach can be pretty handy if you ever need to process large quantities of records and you need even more speed than what Map Reduce gives you. You would need to develop your Suitelet in a way that even if something goes wrong you have a way to identify the errors and retry the operations. Additionally, you would need to get a tool that bypasses the browser restrictions such as Apache JMeter and configure it if you need to pass any data to the Suitelet.

Anyways, the difference is huge. Basically you could process 1 million records in 40 mins in the Suitelet vs 5:30 hrs in a Map Reduce… and this is in Sandbox, go figure how faster this would be in Production.

You are not crazy, SS2.0 External Suitelets don’t run clientside code

July 6, 2017 Adolfo Garza Comments 446 comments

Hey guys, just letting you know that I encountered an issue recently. I was trying to create a Suitelet “Available without Login” that uses a form and I was attaching a button and a clientscript to it, but guess what? The button doesn’t work. I checked the console and every time I call the button I get “require is not defined” error:

So I stripped the suitelet to the most barebones version and I still got the error. I verified with others and it seems to be a defect from SS2.0 External Suitelets.
At the end of the day I was able to run the code by hacking the dom like so:

form.addButton({

id : 'custpage_mybutton',

label : 'MyButton',

functionName : 'runButtonClickAction'

});

var fileContents = file.load(5835).getContents();

var field = form.addField({

id: 'custpageinjectcode',

type: 'INLINEHTML',

label: 'Inject Code'

});

field.defaultValue = "<script>" + fileContents + "</script>";

and as the clientscript file I have this:

$('custpage_mybutton').onclick = function(){ runButtonClickAction(); } //Removes onclick function that fucks with require

function runButtonClickAction(){

alert('Button clicked');

}

Totally not recommended, but just throwing it out there.

Ursus Code

Browsed by
Author: Adolfo Garza