Member Avatar for frankenfrank

What are the things that a server side programmer should be aware of that a client side programmer should not?
and what are the things that a client side programmer should be aware of that a server side programmer should not?

  • 3 Contributors
  • 2 Replies
  • 136 Views
  • 4 Months Discussion Span
  • Latest Post Latest Post by ugi.nagesh

Dani AI

Generated

As and touched on, the practical difference comes down to execution environment and the trust boundary: client code runs in someone else’s browser/device and is visible to the user; server code runs in an environment you control and is the authoritative source of truth. That simple distinction drives very different responsibilities.

Server-side responsibilities to focus on include: authoritative validation and sanitization, data integrity and transactions, authentication/authorization, secret management, logging/monitoring, scaling and capacity planning, rate limiting, and safe API design. Server code must assume hostile or malformed input, be resilient under load, and protect persistent data. Operational concerns—deployment, backups, SSL/TLS termination, and centralized logs—are primarily server-side problems.

Client-side responsibilities are mostly about user experience and working well in varied runtime conditions: fast, responsive UI; optimistic updates and graceful degradation; offline/low-bandwidth support (service workers); minimizing payload size; cross-browser compatibility and feature detection; accessibility and SEO considerations for public pages. Client code is also the main surface for XSS and must avoid storing secrets where possible. Validation on the client is for UX only; never rely on it for security.

A good rule: duplicate validation (client for UX, server for authority), keep secrets and business rules on the server, and design APIs to be stateless where practical. For concrete security guidance see the OWASP Top Ten and, for browser-specific features like CORS and cookie SameSite behavior, see MDN: CORS and SameSite cookies.

Recommended Answers

All 2 Replies

Member Avatar for crescendo

Server side means all the math and calculations will be done on the server, whereas client side will be on the user/client machine. For security and integrity of the data, server side is usually better since the end user will not be able to see or manipulate the data that gets sent back to the server.

Member Avatar for ugi.nagesh

Server side programming :
Where the code will be executed and maintained in the server side. We will use the server side programming when performing the business logics/complex calculations etc..

ex: C#, Vb.NET etc...

Client Side Programming :

We wil use the client side programming to perform the validation and show the message to the user in the client side. Code will be validated in the client machine

EX: JavaScript etc...

Hope this is clear for your

Edited by ugi.nagesh
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.