DEV Community

loading...
Cover image for Serverless or Server?

Serverless or Server?

cdthomp1 profile image Cameron Thompson ・1 min read

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!

Discussion (4)

pic
Editor guide
Collapse
arnoson profile image
arnoson • Edited

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.

Collapse
cdthomp1 profile image
Cameron Thompson Author

This is an interesting take, I haven't really seen PHP being used. What do you do to self host?

Collapse
arnoson profile image
arnoson

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.

Thread Thread
cdthomp1 profile image
Cameron Thompson Author

That's awesome! I will have to look more into webspaces! Thanks for your input, arnoson!