and Plesk another very good hosting control panel that we use:
1 Like
But as I understand it manually “implementing” node.js while using Wappler’s proprietary connector extension is a tutorial in itself.
Node.js is just starting to be considered by many normal php/mysql linux hosting services but usually requiring a completely different account.
Isn’t the magic of node.js only fully realized when Wappler adapts their database connector extension to fully implement its potential?
Yes when we add nodejs support to Server Connect and the database connector then you will fully unleash its potential in Wappler.
For hosting the final nodejs site you still need a hosting that supports it - hence the solutions above.
1 Like
Thank you, again!
I’m super excited for this feature within Wappler as I left the PHP world many years ago for JavaScript.
https://zeit.co/now have an amazing service with super simple deployment. Their team is also responsible for Micro (minimal framework) and Next.js, possibly the most popular project within the React community atm.
Unfortunately they don’t include database hosting.
I’m also a fan of the team behind https://render.com/
Why is nodeJS so important for people?
Don’t get me wrong. I know nodeJS is newer, trending and has some neat features. But for the great majority of websites people tend to build PHP beats nodeJS performance.
Are people just being carried away by novelty and trend?
PHP is not going anywhere anytime soon.
2 Likes
Its one because it “can” be more performant but I think the biggest plus to it is that it allows you to use 1 language on the front and back end. Your using Javascript everywhere. Obviously doesn’t really matter to us inside wappler but thats a big plus if you are writing bare code.
Agreed, but yeah I was refering to wappler server connect. There will be a drop in performance against using PHP for content based sites. 90% of Wappler sites?
I haven’t seen any game or chat based apps created with Wappler that can take advantage of nodeJS.
In any case, I don’t mind it of course
. I was just wandering why the fuss for Wappler support from a Wappler user perspective 
I would see a clear advantage for Wappler team to move to nodeJS if it was the only stack they maintained. So app connect and nodeJS. But having to maintain 4 server stacks and integrate them with app connect seems overkill…
1 Like
Agreed also It does seem that way but I am sure they have a reason behind it. But I believe it does have its drawbacks because when they implement a server connect function they have to then make that language agnostic and program the same thing for ASP and PHP (and then eventually node). In the same token it makes it powerful in the way that since it generates useable code that means you can provide a stack for a customer that may want it specially in ASP, PHP or Node so could help those that are freelancers and/or development houses win more business (which I think may possibly be the majority of power users at the moment but thats an assumption!)
The more server technologies we support, more happy customers we will have
Node.js is really popular nowadays especially for apps related to heavy I/O, real-time data etc. where PHP is slower. Also Node.js has been requested a lot recently - so why not support it when people ask for it? the features integrated in Wappler are community driven, that’s Wappler’s philosophy.
3 Likes
Yeah. Not challenging at all your way of creating the roadmap. Actually it’s one of the things I like the most about Wappler’s philosophy.
I am just challenging users as to why they want it. Most of the sites and questions I’ve seen here are about content driven sites and nodeJS performs worse in that particular scenario. Maybe this is not well known by Wapplers?
Of course I am new here and I am probably missing a lot of things going on.
I do have a real-time project in mind so I will take good advantage of nodeJS when you guys implement it. But will probably stick with PHP for my current projects as they are content based.
2 Likes
I personally am waiting for node.js for the project I am working on. I must have real time updates.
1 Like
Will wappler add new components that take advantage of nodejs multithreading, asynchronous execution and speed?
Besides adding nodeJS runtime capabilities what can we expect from Wappler?
1 Like
Actually the biggest advantage of NodeJS and its speed is that it isn’t that much multi-threading but uses a single thread event loop.
That makes it outperform even PHP on many occasions:
But of course both have their place in web development. However when moving towards to more API oriented architectures, NodeJS seems to be a winner.
I understood nodeJS had worse performance for DB operations. Is this not anymore the case?
To my knowledge that are no DB performance issues with nodejs. It all depends on the database and it’s drivers.
Where did you got this from?
Some benchmarks I saw time ago in stack overflow and some website.
This one for instance (unfortunately in Spanish)
https://static.thinkmobiles.com/uploads/2017/09/php-vsp-node-js-first-test-php.jpg
https://static.thinkmobiles.com/uploads/2017/09/Nodejs-vs-php-first-test-nodejs.png
But you know I am pretty sure I can find a benchmark that says the opposite 
Node has a large amount of packages you can install that are fairly well supported and recent. Plus you can learn one language and use it sever side and client side. It also works well for Electron apps.
2 Likes
Are the team able to share an approximate timeframe for node?
1 Like
Sorry to nag - I wondered if you can give any sort of approx timeline for node? I have a half finished project I would like to have a go at finishing - however its all node / js. Even if its a long term thing it would be great to know how likely we are to see this in the next months / year etc. Thanks!
1 Like