Why is there no strong Ecommerce platform for node.js?

Question

JavaScript

The other day we transferred a highly loaded (550,000 goods and services) online store (auction) from opencart to node.js. We took meteor.js as a basis, which we added on our own. At the reactive front. As a result, the increase in productivity is more than two and a half times. I would like to have a ready-made system out of the box, written on a node, specifically for ecommerce, but one was not found (from worthy ones). Question: why, given the advantages of the node in working with streaming data, is there still no such platform?

Answer 1

The other day we transferred a highly loaded (550,000 goods and services)

The load is not the quantity of goods.
For modern databases, even on weak hardware, this is not a burden, but ridiculous.
The load is the number of visitors.
Even on 100 products, if a large number of visitors, the load can be many times greater than yours.
On Ruby, Node, Go, Java, Python, as a rule, they make decisions for themselves. Ready - a rarity.
Ready-made solutions - exist as a rule in PHP.
This is how this world works.
You can, of course, philosophize about the reasons for this, for example, about what a typical programmer is like in this or that field of activity, and from this you can logically deduce - and why it is so.
Or just look at the fact - if you make a completely turnkey solution not in PHP, then with a high probability it will not be in demand by a large number of people, your consumers will only be niche.
Hence the downside - there are probably ready-made solutions of the type you are interested in on Node, etc. They simply cannot be. You just haven't found them. This is not such a mass product that they are talked about on every corner, like, for example, about OpenCart.

Answer 2

Because no matter how you write on node.js, any more or less complex application turns into procedural noodles. There are no abstractions and type polymorphism, you have to depend on specific implementations. In the meteor on which you wrote your application, there is no di container, everything falls into the global scope, mongo is used, transactions between documents / collections are not supported, strong coupling, hard to cover with tests.
The impression of this all that returned to the early 2000s. We need to wait until the ecmascript specification is finished to a sane state. But I think that by that time in the same php there will already be asynchrony out of the box, especially since the developers have plans for this.

Answer 3

Maybe someone tried https://github.com/reactioncommerce/reaction ?

Answer 4

How much did such an alteration cost and how long did it take, if not a secret? In general, simply because the existing solutions cover 95% of the market needs. The same opencart was created for small stores, although people finish the engine for a large number of goods. A large store can be washed down on magenta, having previously dealt with it. Tighten caching, this and that and get the same result as you have with more maintainability. Moreover, Magento and Bitrix and all other engines were born and solved the problems of developers before the appearance of the node. Yes, and it is more profitable for a developer to work with magenta or another system instead of cycling on a node.

Answer 5

Because 99% of php hostings
are only VPS, but you still need to administer them.
Ready-made services tailored for a node (like Heroku) are even more expensive than VPS.
In short, no need. PHP is enough for everyone.

Answer 6

Because it's javascript