Walmart.com has been migrated to node.
“Over the course of the last year, Walmart.com — a site that handles 80 million monthly visitors and offers 15 million items for sale — migrated to React and Node.js. In the process of this transition, the WalmartLabs team built Electrode, a React-based application platform to power Walmart.com. It’s now open sourcing this platform.”
https://techcrunch.com/2016/10/03/walmartlabs-open-sources-the-application-platform-that-powers-walmart-com/
At 4 minutes 25 seconds into the linked talk (
https://vimeo.com/180426333), Alex Grigoryan explains why Walmart migrated to node:
"So we were currently on Handlebars, Java and Backbone. And we really wanted a lot more scale. We wanted to leverage a lot more requests per second, be more performant, we wanted our developers to be a lot more productive, and we're going through those numbers later on in the presentation. And most of all we wanted reusability. We wanted the ability to leverage components across different brands."
You can also find articles about node success stories at large companies here:
·
https://nodesource.com/blog/how-massive-companies-use-node-js-at-scale/
·
https://www.netguru.co/blog/top-companies-used-nodejs-production
·
https://www.brainvire.com/the-success-story-of-5-retailers-that-have-embraced-node-js/
There are also complaints about node:
https://www.infoworld.com/article/3153225/javascript/nodejs-success-exposes-its-weaknesses.html
But these complaints are not about node performing poorly. They have more to do with having a lot of modules to choose between, dependencies between modules, and security of the modules and the apps being written. Also, getting from hello world to mastery can be trickier than anticipated.
Look, if people don’t want to use node, then don’t use node. If people want to think node is slow or doesn’t have a proven record of good performance at high levels of concurrency, then feel free to think node is slow and doesn’t have good performance. I’m not here to change your minds.
I plan to take my future discussions of node to the Midrange.com OpenSource list. I several people on this list also on that list. I’m not looking for a new crowd. The OpenSource list just seems to have a higher percentage of discussions about node on the IBM i. There are probably a lot of people on this list using PHP, CGI and other technologies that are sick to death of all the node posts here. Sorry about that.
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: Tuesday, April 10, 2018 5:30 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] [EXTERNAL] Re: ibm_db node module and IBM Data Server Driver
I've been vexed by a number of red herrings that have been presented in
this discussion. Walmart migrated a handful of "customer experience"
interfaces in their e-commerce site from JEE to Node.js, but they haven't
"quit" their use of Java.
Quite to the contrary, front-end Node applications such as "add to cart"
and "checkout" still rely on Java based web services that provide
middle-tier infrastructure, colloquially named "uServices" between Node
and Walmart's back-end database. Here are a couple references:
https://medium.com/walmartlabs/migrating-large-enterprise-to-nodejs-6c38523d2b33<
https://medium.com/walmartlabs/migrating-large-enterprise-to-nodejs-6c38523d2b33>
and
https://vimeo.com/180426333<
https://vimeo.com/180426333>
Walmart's Alex Grigoryan expressed that the migration to Node initially led
to performance problems, which they later resolved by adding a caching
layer to their Node framework.
Something like 95+ percent of Walmart's e-commerce site is static content,
served by Akamai and other content networks that use mostly Apache and IIS
for delivery over HTTP.
The formatted streams that are generated by Node and delivered to Walmart's
e-commerce clients are very small when compared to the work that is
occurring in Java middle-tier, IBM i back-end database, and by Walmart's
content delivery providers. Likewise, the functional scope of Walmart's
e-commerce site is small when compared to Walmart's internal applications.
Please see my inline response that follows.
On Tue, Apr 10, 2018 at 10:17 AM, Kelly Cookson <KCookson@xxxxxxxxxxxx<mailto:KCookson@xxxxxxxxxxxx>>
wrote:
The following are not rhetorical questions. I would genuinely appreciate
hearing from you (on list or off list).
· Is anyone using CGI on IBM i for very high volumes of concurrent
requests similar to, say, Walmart, eBay, PayPal, Amazon Brand Stores, or
Netflix?
I wrote a plug-in for the IBM i HTTP server that enables it to work as a
message broker between HTTP clients and back-end ILE servers. Most of our
IBM i HTTP instances provide a messaging interface in addition to serving
static content. Our messaging interface is similar to Walmart's use of
Kafka, which bridges Node.js clients with middle-tier Java services.
We've logged up to 40 million requests for dynamic content per day in a
production environment on a 4-core IBM i system using this type of
interface. I'm not aware of any interface on any platform that performs
better or scales better than this.
· Has anyone used both CGI and node on the IBM i and can speak
anecdotally to comparisons between the two?
Your question seems like another sidetrack given the context of this and
previous discussions. You've expressed several times that you want a bridge
between dotNet Core and IBM i resources (i.e. database, commands, programs).
What would be better, one short bridge between dotNet core and IBM i
resources? Or should you insert another bridge that includes a hop to
Node.js and some middle-tier applications, and thus increase the distance,
the hops,and the latency between dotNet core and IBM i?
If you'd like to follow Walmart's example, you might propose migrating some
of your .Net applications to Node.js.
--
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
