For what is it worth, my opinion.
Node has many performance and feature benefits, not least sockets which allow dynamic data refreshes across multiple users.
I started to use Docker as this simplified the deployment of node to servers until i discovered how much Docker can screw up when it goes wrong (loss of security credentials is a nightmare scenario)
I use Node for most projects now, i no longer use docker, i use a VPS which is pretty simple to set up (i use cPanel)
2.49$ per month hetzer - docker server - server does not care if you install PHP or NODEJS - same price - one docker on the develper machine (we have Mac books works perfect even working in a cafe) then publish it to production server to hetzer - fast as hell never an issue - need power upgrade to a bigger server 10 euro or so ā¦
Do you have a link to their site? I canāt find anything. And does it have to use Docker?
I believe you grab a Cloud package then simply install Docker @brad, I may be wrong but that seems the route to meā¦?
Itās actually in wappler - go to Proejct settings - targets Choose docker , in connection choose remote, click on manage plus for new provider, select hetzer in provider - there you can create a new account and you get 20 Euro as a gift (guess wappler made a deal with them) good luck and happy developing
Thanks @yellowsnow. I like to know ahead of time what Iām paying. I will explore it though. I assume like everywhere else that if you want a database itās extra cost?
This topic should really be split up. Didnāt mean to hijack the thread.
Nope you just include the MySQL version you want in your Container Image and deploy!
See Docker as a sort of host Brad, within it you can add pretty much whatever you want. PHP, Node, MySQL/Maria/Postgres, etc etc. And a whole lot more! Build the stack you want from what you know, then it functions the same as any other host you have used. If you want to change something just include it in your environment, deploy, and youāre away.
Everything you can deploy in a docker is included - same as a docker in vultr or DO. Only hetzer is a more hosting oriented provider also has a DNS service for the deployed docker etc
It all comes down to you clients requirementsā¦ and budget.
The only thing that is missing for us using php ā¦ is real-time dataā¦
Reasons why we stick with php.
-
Most of our client has come years with usā¦ and updating and scaling site with php is just so much easierā¦ than having to re-do a complete siteā¦
-
we donāt host all our clients sites - some of them have hosting before they became our clients. Most of these clients are small - medium companies, so they have opted for shared hosting with php ā¦ that is cheapā¦ as they dont see the benfit of having a vps just for them. 90 USD Ā± compared to shared hosting Ā± 5 - 10 USDā¦
-
If you however host all your clients sitesā¦ and can offset the cost for a VPS then by no means do thatā¦ and then node js makes senseā¦ as it gives you more options.
-
We get new clients everyday with * shared hosting setup ā with emails and so onā¦ and they are happy with the hostingā¦ they only want to use us for dev workā¦ now try to tell that client to move their hosting and re-setup all their email accounts and pay more just for real-time data they might not useā¦ its a catch 22ā¦
-
If you have large clients with good money that can afford a dedicated server from the word goā¦ then nodjsā¦ but that is not the case for usā¦
Hehe, I said right at the beginning that you'll get a mixed response
I think the thing to remember is that Node and PHP are alternatives, itās not a competition between them, use whichever suits your particular needs. Both have strengths and weaknesses. and of course we must also mention .NET. Seems less popular but certainly a powerful platform.
I tried very hard not to participate.
Hahahah.
I wasnāt going to add anything that I havenāt said before and probably a few snowflakes would get offended with my words.
Alsoā¦voodoo.
I was tempted to start a timer to see how long it would be before @JonL posted. Way longer than Iād predicted so a big well-done for resisting!
i think (@JonL nL) he was just out of town buying milk or somethingā¦
Purely in theory, this sounds quite interesting. But if we approach it from a practical point of view, it seems to me that there are more reliable and proven approaches to solving the problem you have voiced, which can be implemented with Wappler right now. You simply create an independent application on node js, which serves a strictly defined functionality (for example, sockets on a certain page), and create a connection with your main application using the API. This approach is called microservice architecture, and is often used in large projects.
P.S. The only thing that you will have to tinker with at the moment using this approach is routing. Wappler will not help to link two different applications at the route level. Most likely, you will have to solve this problem at the server level of your hosting (for example, nginx). And it seems to me that if the Wappler gave a toolkit to link different applications at the route level, it would be very cool.
Iāll give you that one lol