Clustered Solutions
-
Hi Guys I'm starting work on a project that is a larger scale to anything I've done before, and it is probable that we will be deploying it to clutered servers... Do I need to do anything special to account for this in the app? or would I just carry on developing as though it was a single server web application? Thanks in advance :-D
oooo, the Jedi's will feel this one....
-
Hi Guys I'm starting work on a project that is a larger scale to anything I've done before, and it is probable that we will be deploying it to clutered servers... Do I need to do anything special to account for this in the app? or would I just carry on developing as though it was a single server web application? Thanks in advance :-D
oooo, the Jedi's will feel this one....
You must have system intergration plan document/deployment document(deployment environement related stuff doucmented)/design documents in your project which should be having all these information. Your question does not reflect any specific technical query however which is general to technical forum. Please correct me if I am wrong.
Thanks, Arindam D Tewary
-
You must have system intergration plan document/deployment document(deployment environement related stuff doucmented)/design documents in your project which should be having all these information. Your question does not reflect any specific technical query however which is general to technical forum. Please correct me if I am wrong.
Thanks, Arindam D Tewary
Thank you for your reply. I'm sorry. I don't think I was very clear with what I'm after. This is my first large scale application. Everything else I have done has been happy running on a single server. This project is to run on clustered servers, so I was wondering if I would need to code to account for the multiple servers (Data Access etc), or if I should just code as I would have for a single server solution? I don't know if the cluster would take care of itself, or if I need to take care of it programatically. This is probably a silly question, but I'm self taught, and have never tackled this kind of thing before. (I may be in a little over my head... :-O )
oooo, the Jedi's will feel this one....
-
Thank you for your reply. I'm sorry. I don't think I was very clear with what I'm after. This is my first large scale application. Everything else I have done has been happy running on a single server. This project is to run on clustered servers, so I was wondering if I would need to code to account for the multiple servers (Data Access etc), or if I should just code as I would have for a single server solution? I don't know if the cluster would take care of itself, or if I need to take care of it programatically. This is probably a silly question, but I'm self taught, and have never tackled this kind of thing before. (I may be in a little over my head... :-O )
oooo, the Jedi's will feel this one....
If your application is deployed over multiple server then you might keep in mind some below mentioned points as a developer. (1) There are load balancing software which handles incomming request. (2) if you know that your application redirects http request across multiple domain, then you should use Response.Redirect(). Otherwise server.transfer for new redirection in case you need that. (3) Even if you use session variable you have to store Session data in a centralised database/server so that redirtion across multiple server(domain) does not loose any session data. I would post if some more points I can provide to you in this thread.
Thanks, Arindam D Tewary
-
If your application is deployed over multiple server then you might keep in mind some below mentioned points as a developer. (1) There are load balancing software which handles incomming request. (2) if you know that your application redirects http request across multiple domain, then you should use Response.Redirect(). Otherwise server.transfer for new redirection in case you need that. (3) Even if you use session variable you have to store Session data in a centralised database/server so that redirtion across multiple server(domain) does not loose any session data. I would post if some more points I can provide to you in this thread.
Thanks, Arindam D Tewary
Thats a good point about the session data. I didn't think about that. I suppose session data would no longer be any use unless stored in a database or maybe in cookies? to cope with the possibility of a different server serving up your newly navigated page from the previous page. That has given me a good start. Thank you. :-D
oooo, the Jedi's will feel this one....
-
Hi Guys I'm starting work on a project that is a larger scale to anything I've done before, and it is probable that we will be deploying it to clutered servers... Do I need to do anything special to account for this in the app? or would I just carry on developing as though it was a single server web application? Thanks in advance :-D
oooo, the Jedi's will feel this one....
See As per development point of view, if your application is going to be on multiple web servers, then you have take extra care about those items who resides in server memory like session,application variables etc.You should use DB to store most of the data. Application variables should not be used in case of multiple servers. And for session, it should not be in
InProcmode. For details about session, Exploring Session in ASP.Net Rest thing like how your application is going to accessed by endusers ie url, how you are going to connect to DB and other server if there, should be taken care by H/W guysCheers!! Brij Check my latest Article :Exploring ASP.NET Validators
-
See As per development point of view, if your application is going to be on multiple web servers, then you have take extra care about those items who resides in server memory like session,application variables etc.You should use DB to store most of the data. Application variables should not be used in case of multiple servers. And for session, it should not be in
InProcmode. For details about session, Exploring Session in ASP.Net Rest thing like how your application is going to accessed by endusers ie url, how you are going to connect to DB and other server if there, should be taken care by H/W guysCheers!! Brij Check my latest Article :Exploring ASP.NET Validators
Great. Thank you. :-D
oooo, the Jedi's will feel this one....
-
Great. Thank you. :-D
oooo, the Jedi's will feel this one....
your welcome :)
Cheers!! Brij Check my latest Article :Exploring ASP.NET Validators
-
Thats a good point about the session data. I didn't think about that. I suppose session data would no longer be any use unless stored in a database or maybe in cookies? to cope with the possibility of a different server serving up your newly navigated page from the previous page. That has given me a good start. Thank you. :-D
oooo, the Jedi's will feel this one....
You are welcome. :)
Thanks, Arindam D Tewary