This post is to generate some discussion on why you prefer to use either the traditional backend (NodeJS, EfCore/ASP, PHP, etc.) or the Serverless Architecture.
Let me know you thoughts in the comments below on why you use what you use!
For further actions, you may consider blocking this person and/or reporting abuse
Node.js doesn’t stop from running other operations because of Libuv, a C++ library responsible for the event loop and asynchronously handling tasks such as network requests, DNS resolution, file system operations, data encryption, etc.
What happens under the hood when Node.js works on tasks such as database queries? We will explore it by following this piece of code step by step.
Ben Halpern -
Pubudu Jayawardana -
Matt Morgan -
GrahamTheDev -
Once suspended, cdthomp1 will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, cdthomp1 will be able to comment and publish posts again.
Once unpublished, all posts by cdthomp1 will become hidden and only accessible to themselves.
If cdthomp1 is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Cameron Thompson.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag cdthomp1:
Unflagging cdthomp1 will restore default visibility to their posts.
Top comments (4)
For simple websites (not web apps) I still prefere a PHP based CMS (like Kirby, Grav or Processwire). Nearly every webspace supports PHP and I like to self host as much as possible.
This is an interesting take, I haven't really seen PHP being used. What do you do to self host?
Usually I'll just rent a webspace for a client if he/she hasn't one already. A webspace comes without the responsibility of a full server and is usally really cheap (2-5 Euros a month in germany, domain included). Normally I make sure that the webspace supports SSH, than I can "deploy" the website with a simple npm script using rsync. Most webspaces also support git, so even such a setup would be possible. Flatfile-CMS like Kirby and Grav even do not need a database. This really worked well in the past. No complicated setup, no AWS, no Webhooks and most CMS support caching so your website should be as fast as a static one.
Of course if a website is slightly more complicated and you need a javascript framework like vue it gets a bit tricky, but there are also headless PHP CMS like directus and in other CMS you can build basic json endpoints. Another approach I woul like to test in the future is using alpine.js for cases where a website needs to be a bit more interactive but an SPA would be an overkill.
That's awesome! I will have to look more into webspaces! Thanks for your input, arnoson!