Yes, Node.JS is not everything Walmart is doing. They have a lot more they are doing in terms of building a cloud of services.
My comments earlier-which are indeed shallow-is that Walmart was able to handle high volumes of requests (around half of their online Black Friday traffic) with their CPU hovering around 1%. Other companies have also been able to use Node to process more requests more quickly and reduce the servers they use because they don't need as much CPU. The point I was attempting to make is that, in real-life situations, Node is fast, scales in terms of handling high volumes of requests, and keeps CPU relatively low.
I did not mean to imply that Node was anything more than a piece in a puzzle. I often refer to Node as a niche technology. It's very opinionated about how it does things, and it's definitely not the right tool for all projects. But when Node is used appropriately, it can be very successful. (So can other tools. Just saying Node is one tool in the toolbox.)
Thanks,
Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<
http://www.dotfoods.com>
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Friday, March 23, 2018 11:05 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WEB400] REST web service APIs
Nadir,
Thanks for your response. I followed the link that you provided and further
linked to the following:
https://www.ibm.com/cloud/integration<
https://www.ibm.com/cloud/integration>
Halfway down that page there is a link to a 3 minute video with the
following text:
"Learn how Walmart is building a platform driven by APIs to provide its
developers with a self-service portal that supports faster development and
helps Walmart deliver new services and improvements at the speed of
business."
The technicians at Walmart briefly discuss the benefits of their API
architecture. That intrigued me because we've had some shallow comments on
this list this past week about Walmart using Node.js for a high-volume
shopping site. That video suggest that there is a lot more to the story
than just switching to Node.js.
For those who favor an XMLSERVICE interface over an API interface, I'm
curious how you handle end-user access privileges? XMLSERVICE, ODBC, JDBC,
and the like allow clients to execute any SQL statement against any
database files, to call any program, to run any command. What is your
preferred way of controlling that?
With APIs, I envision a service that checks a list to see if users have
been granted authority to an API, and providing an appropriate error
message if otherwise.
Nathan.
On Fri, Mar 23, 2018 at 8:35 AM, Nadir Amra <amra@xxxxxxxxxx<mailto:amra@xxxxxxxxxx>> wrote:
Hi, it is a viable alternative. There are multiple ways to do this and
you may choose the best one that suits your needs. I will also point out
that integrated web services server[1] documents it services via Swagger.
[1] http://www.ibm.com/support/docview.wss?uid=isg3T1026868<http://www.ibm.com/support/docview.wss?uid=isg3T1026868>
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx<mailto:WEB400@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/web400<
https://lists.midrange.com/mailman/listinfo/web400>
or email: WEB400-request@xxxxxxxxxxxx<mailto:WEB400-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/web400<
https://archive.midrange.com/web400>.
midrange.com
