What is the difference between a web application and a client/server application?

Question

I took this from another question I had.

Under appropriate uses for sqlite it has:

Situations Where SQLite Works Well

•Websites

SQLi

Answer 1

"web" applications imply the browser is the client

Client/Server apps imply a custom client app. Think Outlook hooked up to exchange, while it may use the web to connect, it is its own client to the exchange server.

EDIT:

More specific to the sqlite text you posted, what they mean is that client applications shouldn't be accesing your sqllite DB directly, and instead should be using some sort of server side interface (i.e. a json web service)

But that rule of thumb, in my opinion, applies to ALL database engines. If I were using SQL Server or Oracle, I would DEFINIETLY avoid having client apps connect directly to the DB, this has many potential problems, the first being security.

Answer 2

There are a few differences of note:

Web Applications assume the client is a web browser and that communication between the client and server is stateless (HTTP). It also tends to assume that the client is "thin" and very little processing of information is done in the browser.

Client-Server Applications assume the client is a "thick" client and that communication between the client and server maintains state (this isn't necessarily true). Communication can be pretty much any protocol. The old-fashioned client-server, or 2-tier application does have each client connect to the database directly - I would advise against this for various reasons, number one being security. This is probably what the source you posted meant when saying SQLite isn't appropriate.

A 3+tier type of application could still have a with-state client-server communication, but the middle-tier would handle the actual database communication. In this case, latency on the network isn't important and SQLite could work (because it is more like a web app).

Answer 3

Difference b/n Client /server application and web application server

1)Client server applications follow up Two tier architecture, but web server applications follows Three tier or 'n'tier architecture.

2)In client server application we will not use Web servers, but in web server applications same will be used.

3)Client server applications Majorly used in Intranet areas,but web server applications used in Internet areas.

4)Securiry issues are very less in client server as there are Minimum users,but in Web server Security issues are Maximum as end users are more.

5)Performance issues will not be taken in to consideration in client server, but consideration will be done web server applications.

Answer 4

1. Web apps runs on a browser, client-server apps runs as .exe.
2. Web applications run on server, Client-Server apps run on client side.
3. Web application is thin client, client-server app is thick client.
4. Web application does not need to be installed in client system, Client-server apps need to be installed in client system 5.Web apps need low maintenance, client-server apps need high maintenance

http://webvsclientserverbysujan.blogspot.in/2014/01/WebVsDesktoApppbysujan.blogspot.com.html

Answer 5

A "Web Application" is one in which a browser is commonly used as the client. A Web application IS A Client/Server Application. In other words, you could think of a client/server application as a superclass, where the web application is a child class.