Architecture
-
Hi, We are in the process of building a new enterprise application, that would comprise of an Oracle database, and a VB.NET application. Now my request to you all is to suggest the optimal architecture, in terms of technology, stability, maintenance, etc, bearing in mind that we would like to have a multi-tier application, with a thin client, and 1 to n business/persistence layers. The application would be used by users who might be geographically separated. Would appreciate your inputs on: Winforms Vs ASP.NET? Communication, Data persistence, Performance, Any other criterion that you might consider important. Your inputs would be highly appreciated. Cheers/RB
-
Hi, We are in the process of building a new enterprise application, that would comprise of an Oracle database, and a VB.NET application. Now my request to you all is to suggest the optimal architecture, in terms of technology, stability, maintenance, etc, bearing in mind that we would like to have a multi-tier application, with a thin client, and 1 to n business/persistence layers. The application would be used by users who might be geographically separated. Would appreciate your inputs on: Winforms Vs ASP.NET? Communication, Data persistence, Performance, Any other criterion that you might consider important. Your inputs would be highly appreciated. Cheers/RB
RajeevBhatt wrote:
Winforms Vs ASP.NET?
RajeevBhatt wrote:
Communication
RajeevBhatt wrote:
Performance
Windows forms (generally) give a faster, and more direct interactive experience to the user. Development will be easier. You will not be dependent on internet connections (or quality thereof)
RajeevBhatt wrote:
The application would be used by users who might be geographically separated.
This is the key question, and I warmly suggest that you get a more committed answer from the customer.
RajeevBhatt wrote:
Data persistence
In the case of "geographically separated users" ASP.NET (a web application) is much much easier for the application / data administrator(s), and will likely be much cheaper to maintain, and develop in the long run. System updates / patches / fixes go live instantly for all users, and all data returned is "live" at all times.
RajeevBhatt wrote:
Any other criterion that you might consider important.
You should be asking the customer this. (By the way, "customer" can also mean "your boss".)
My advice is free, and you may get what you paid for.
-
Hi, We are in the process of building a new enterprise application, that would comprise of an Oracle database, and a VB.NET application. Now my request to you all is to suggest the optimal architecture, in terms of technology, stability, maintenance, etc, bearing in mind that we would like to have a multi-tier application, with a thin client, and 1 to n business/persistence layers. The application would be used by users who might be geographically separated. Would appreciate your inputs on: Winforms Vs ASP.NET? Communication, Data persistence, Performance, Any other criterion that you might consider important. Your inputs would be highly appreciated. Cheers/RB
It is very, very rude to post the same question in more than one forum! For future reference, decide which forum most suits your question and post it there and only there. In this case either 'General Database' or 'Design and Architecture' would seem most appropriate.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”