Can web application be considered part of client/server architecture?
I am doing a research on client/server architecture and web applications. I've been reading different thoughts and suggestions around the web. Some saying that web applications are not considered client/server architecture apps while others are saying the exact opposite. I was wondering what is actually the right thing and if someone can provide in depth explanation that would be highly appreciated?
web architecture client-server software-design
asked Nov 12 at 12:57
redberry
316
add a comment |
I am doing a research on client/server architecture and web applications. I've been reading different thoughts and suggestions around the web. Some saying that web applications are not considered client/server architecture apps while others are saying the exact opposite. I was wondering what is actually the right thing and if someone can provide in depth explanation that would be highly appreciated?
web architecture client-server software-design
asked Nov 12 at 12:57
redberry
316
add a comment |
I am doing a research on client/server architecture and web applications. I've been reading different thoughts and suggestions around the web. Some saying that web applications are not considered client/server architecture apps while others are saying the exact opposite. I was wondering what is actually the right thing and if someone can provide in depth explanation that would be highly appreciated?
web architecture client-server software-design
asked Nov 12 at 12:57
redberry
316
I am doing a research on client/server architecture and web applications. I've been reading different thoughts and suggestions around the web. Some saying that web applications are not considered client/server architecture apps while others are saying the exact opposite. I was wondering what is actually the right thing and if someone can provide in depth explanation that would be highly appreciated?
web architecture client-server software-design
web architecture client-server software-design
asked Nov 12 at 12:57
redberry
316
asked Nov 12 at 12:57
redberry
316
asked Nov 12 at 12:57
redberry
316
asked Nov 12 at 12:57
redberry
316
asked Nov 12 at 12:57
redberry
316
316
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It depends on the architecture/design of your web application(s). The rule of thumb would be: The client application has to be another piece of software than the (resource) server. There is no "one right way" to design a client/server architecture.
The most common implementations for web based applications are MVC (Model View Controller and SPAs (Single Page Applications).
MVC applications (like ASP.NET or ZendFramework) are applications that are booth rendering the client and handling the business logic in the backend and are not based on a client/server model. (An action in a controller handles a request, loads some data and renders an HTML view as the response).
But: If your MVC Application is acting as a proxy calling a "remote" web service internally (via SOAP or whatever), it should be considered a client application.
As an example: A CRM system is running in an intranet network and provides a data-services for desktop clients. You could write a web application that displays data from those services which is then another client application.
The SPA architecture requires the separation of the server from the frontend, the SPA being the frontend, which in turn is the client application. With this requirement you are basically already implementing a client/server architecture. Let's say an AngularJS frontend and the backend could be a REST service (like ASP.NET WebAPI or Lumen).
The choice of where you host the client application does not affect the client/server architecture, since the applications are still separated on execution: the browser executes the JavaScript SPA on the device of the visitor and calls the service in some data center.
answered Nov 12 at 14:40
Josef Fazekas
30125
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
add a comment |
Web application is a part of client-server architecture. Any implementations have always two or more tiers, so two or more process communicate each other.
You may take a look on my old presentation "Architecture of enterprise (automated) information system - Layers and levels" that shows different client-server architectures including web application case (the slide "Tiers are physical layers (examples)" shows examples).
answered Nov 14 at 12:31
serge
59537
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53262676%2fcan-web-application-be-considered-part-of-client-server-architecture%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It depends on the architecture/design of your web application(s). The rule of thumb would be: The client application has to be another piece of software than the (resource) server. There is no "one right way" to design a client/server architecture.
The most common implementations for web based applications are MVC (Model View Controller and SPAs (Single Page Applications).
MVC applications (like ASP.NET or ZendFramework) are applications that are booth rendering the client and handling the business logic in the backend and are not based on a client/server model. (An action in a controller handles a request, loads some data and renders an HTML view as the response).
But: If your MVC Application is acting as a proxy calling a "remote" web service internally (via SOAP or whatever), it should be considered a client application.
As an example: A CRM system is running in an intranet network and provides a data-services for desktop clients. You could write a web application that displays data from those services which is then another client application.
The SPA architecture requires the separation of the server from the frontend, the SPA being the frontend, which in turn is the client application. With this requirement you are basically already implementing a client/server architecture. Let's say an AngularJS frontend and the backend could be a REST service (like ASP.NET WebAPI or Lumen).
The choice of where you host the client application does not affect the client/server architecture, since the applications are still separated on execution: the browser executes the JavaScript SPA on the device of the visitor and calls the service in some data center.
answered Nov 12 at 14:40
Josef Fazekas
30125
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
add a comment |
It depends on the architecture/design of your web application(s). The rule of thumb would be: The client application has to be another piece of software than the (resource) server. There is no "one right way" to design a client/server architecture.
The most common implementations for web based applications are MVC (Model View Controller and SPAs (Single Page Applications).
MVC applications (like ASP.NET or ZendFramework) are applications that are booth rendering the client and handling the business logic in the backend and are not based on a client/server model. (An action in a controller handles a request, loads some data and renders an HTML view as the response).
But: If your MVC Application is acting as a proxy calling a "remote" web service internally (via SOAP or whatever), it should be considered a client application.
As an example: A CRM system is running in an intranet network and provides a data-services for desktop clients. You could write a web application that displays data from those services which is then another client application.
The SPA architecture requires the separation of the server from the frontend, the SPA being the frontend, which in turn is the client application. With this requirement you are basically already implementing a client/server architecture. Let's say an AngularJS frontend and the backend could be a REST service (like ASP.NET WebAPI or Lumen).
The choice of where you host the client application does not affect the client/server architecture, since the applications are still separated on execution: the browser executes the JavaScript SPA on the device of the visitor and calls the service in some data center.
answered Nov 12 at 14:40
Josef Fazekas
30125
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
add a comment |
It depends on the architecture/design of your web application(s). The rule of thumb would be: The client application has to be another piece of software than the (resource) server. There is no "one right way" to design a client/server architecture.
The most common implementations for web based applications are MVC (Model View Controller and SPAs (Single Page Applications).
MVC applications (like ASP.NET or ZendFramework) are applications that are booth rendering the client and handling the business logic in the backend and are not based on a client/server model. (An action in a controller handles a request, loads some data and renders an HTML view as the response).
But: If your MVC Application is acting as a proxy calling a "remote" web service internally (via SOAP or whatever), it should be considered a client application.
As an example: A CRM system is running in an intranet network and provides a data-services for desktop clients. You could write a web application that displays data from those services which is then another client application.
The SPA architecture requires the separation of the server from the frontend, the SPA being the frontend, which in turn is the client application. With this requirement you are basically already implementing a client/server architecture. Let's say an AngularJS frontend and the backend could be a REST service (like ASP.NET WebAPI or Lumen).
The choice of where you host the client application does not affect the client/server architecture, since the applications are still separated on execution: the browser executes the JavaScript SPA on the device of the visitor and calls the service in some data center.
answered Nov 12 at 14:40
Josef Fazekas
30125
It depends on the architecture/design of your web application(s). The rule of thumb would be: The client application has to be another piece of software than the (resource) server. There is no "one right way" to design a client/server architecture.
The most common implementations for web based applications are MVC (Model View Controller and SPAs (Single Page Applications).
MVC applications (like ASP.NET or ZendFramework) are applications that are booth rendering the client and handling the business logic in the backend and are not based on a client/server model. (An action in a controller handles a request, loads some data and renders an HTML view as the response).
But: If your MVC Application is acting as a proxy calling a "remote" web service internally (via SOAP or whatever), it should be considered a client application.
As an example: A CRM system is running in an intranet network and provides a data-services for desktop clients. You could write a web application that displays data from those services which is then another client application.
The SPA architecture requires the separation of the server from the frontend, the SPA being the frontend, which in turn is the client application. With this requirement you are basically already implementing a client/server architecture. Let's say an AngularJS frontend and the backend could be a REST service (like ASP.NET WebAPI or Lumen).
The choice of where you host the client application does not affect the client/server architecture, since the applications are still separated on execution: the browser executes the JavaScript SPA on the device of the visitor and calls the service in some data center.
answered Nov 12 at 14:40
Josef Fazekas
30125
answered Nov 12 at 14:40
Josef Fazekas
30125
answered Nov 12 at 14:40
Josef Fazekas
30125
answered Nov 12 at 14:40
Josef Fazekas
30125
30125
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
add a comment |
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
Fazeksas That helps very much! Just to clarify - Lets say Im building web application (AngularJS/React/Etc) which front-end handles operations such as writing data in MySQL database hosted in a cloud & based on that the server will do something with the data like sending alerts etc. Is that client/server architecture application or something else?
– redberry
Nov 12 at 14:56
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
If you are sending the data directly to the database then i would say it's not a client/server architecture. That's because i separate my data sources from the business logic when designing an application. I guess the application that sends the alerts does so by polling, that would make that application a standalone application. If you are sending the data from your frontend to a server which then saves the data to a datastore and sends alerts, it would be a client/server architecture.
– Josef Fazekas
Nov 12 at 15:05
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes what I meant was sending data from the front-end to a server which would save the data into a database & than the server would do something else like send alerts or whatever back is client/server architecture right?
– redberry
Nov 12 at 15:21
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Yes, that's correct :)
– Josef Fazekas
Nov 12 at 15:56
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
Thank you very much for taking time to explain this! Appreciated!
– redberry
Nov 12 at 15:59
add a comment |
Web application is a part of client-server architecture. Any implementations have always two or more tiers, so two or more process communicate each other.
You may take a look on my old presentation "Architecture of enterprise (automated) information system - Layers and levels" that shows different client-server architectures including web application case (the slide "Tiers are physical layers (examples)" shows examples).
answered Nov 14 at 12:31
serge
59537
add a comment |
Web application is a part of client-server architecture. Any implementations have always two or more tiers, so two or more process communicate each other.
You may take a look on my old presentation "Architecture of enterprise (automated) information system - Layers and levels" that shows different client-server architectures including web application case (the slide "Tiers are physical layers (examples)" shows examples).
answered Nov 14 at 12:31
serge
59537
add a comment |
Web application is a part of client-server architecture. Any implementations have always two or more tiers, so two or more process communicate each other.
You may take a look on my old presentation "Architecture of enterprise (automated) information system - Layers and levels" that shows different client-server architectures including web application case (the slide "Tiers are physical layers (examples)" shows examples).
answered Nov 14 at 12:31
serge
59537
Web application is a part of client-server architecture. Any implementations have always two or more tiers, so two or more process communicate each other.
You may take a look on my old presentation "Architecture of enterprise (automated) information system - Layers and levels" that shows different client-server architectures including web application case (the slide "Tiers are physical layers (examples)" shows examples).
answered Nov 14 at 12:31
serge
59537
answered Nov 14 at 12:31
serge
59537
answered Nov 14 at 12:31
serge
59537
answered Nov 14 at 12:31
serge
59537
59537
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53262676%2fcan-web-application-be-considered-part-of-client-server-architecture%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
