DEV Community

Mohamed Sameer
Mohamed Sameer

Posted on

Hello developers πŸ”₯ I have four questions for you.

Question 1. Client side rendering or Server side rendering? πŸ€”

Basically in Web applications, we have two approaches either we can render views on server side using template engines like jade,ejs,etc... or we can render views on client side using SPA frameworks (Angular/React/Vue).

Which one you prefer and which one is good to use?
Backend For JSON API only or for even rendering views

Question 2. How you make project structure? πŸ€”

Backend and frontend code in same project
Backend is separate project and front end is separate project

I actually use Both Backend and Frontend in same project, I create REST APIs using node/express and i use jade as server side templating for views.

Many developers creating Backend as a separate project and only writing apis and creating Frontend as a separate project and by using Angular,React,Vue they consuming that api.

Question 3: Hosting your application? πŸ€”

While you hosting your applications on production? Will you host backend and front end in separate servers?

Question 4: SQL queries or ORM? πŸ€”

I love ORM and i use sequelize on my projects, Do you use ORM or Plain SQL queries for your applications?

Discussion (2)

nathanbland profile image
Nathan Bland • Edited

These are some solid questions, but as with most things programming the answer is usually.. It depends. Here is my opinion in general though.

  1. SSR vs SPA? Both. SSR improves SEO and lighthouse scores, not to mention will make your site load faster for users, which is critical. There are some cases, static sites come to mind, where SPA functionality isn't needed. Private project or internal system? SSR might not be needed. It just depends.

  2. Project Structure: Oh boy. Again, it depends. If the project is going to have multiple clients - iOS, Android, PWA, desktop - definitely separate. In this case you can write your api code once, and leverage it across all your target platforms without having a mess of one repository. However, if it is only a PWA/web site, one is probably fine, or even preferred to keep a single list of dependencies.

  3. Hosting: Database, for me at least, is always on its own host for security reasons, and its connection string is never in a config file. As for a client vs backend.. Once it depends. Static site? Github pages is all you need anyway. Some dynamic content? One host is probably fine, however beyond this, it is a good idea to do two things. The first being, run your application in a "cluster" mode (pm2 for node comes to mind), so that it can use all the resources available to it. And second, use a load balancer and reverse proxy - those can be the same, such as nginx. This will one, make your application code work less, and two allow your application to be able to scale if it needs to without user impact.

  4. SQL queries on their own are not safe to use, period. SQL prepared statements are better. Usually, ORMs will do the preparing part for you, at the cost of some performance. However, none of this is entirely enough and you should be taking extra steps to validate your user input before it gets handed off to something that is talking to your database. In my experience the utility that ORMs provide is usually worth it, especially once you are used to them, vs the small trade off of performance you might gain from writing it all yourself. They are also probably better tested.

ondrejs profile image

Very quickly:

  1. Clients side rendering -> Less server-side load.
  2. Depends very much on you codebase and other factors.
  3. I do, specifically for security reasons.
  4. Definitely not ORM. It's bad design & idea at the first place (you can see it in bigger projects), but that is only my opinion - make you own!