Architecture
-
Does this not belong in either the 'Design and Architecture' or 'General Database' forums?
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.”
Henry Minute wrote:
Does this not belong in either the 'Design and Architecture'
It does, and the OP has helpfully cross posted there as well.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
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?
Definitely WinForms if you want it to be a thick client app (Or you could use WPF). Go for ASP.net if you want it to run in a browser.
Communication
Yes, I would include some.
Data persistence
Probably a good idea, but not necessary if your users have very good memories.
Performance
The faster you make it the better.
Any other criterion that you might consider important.
It shouldn't crash too much if possible.
Simon
-
RajeevBhatt wrote:
Winforms Vs ASP.NET?
Definitely WinForms if you want it to be a thick client app (Or you could use WPF). Go for ASP.net if you want it to run in a browser.
Communication
Yes, I would include some.
Data persistence
Probably a good idea, but not necessary if your users have very good memories.
Performance
The faster you make it the better.
Any other criterion that you might consider important.
It shouldn't crash too much if possible.
Simon
Simon P Stevens wrote:
It shouldn't crash too much if possible.
Don't you think you're asking a bit too much, here?
We are using Linux daily to UP our productivity - so UP yours!
-
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?
If you can't decide this based on client needs, then you're too stupid to write this thing, just like you're too stupid not to cross post this question.
RajeevBhatt wrote:
Communication
I suggest you try doing this with your client, yes
RajeevBhatt wrote:
Data persistence,
Oh, flat files, CSVs for sure. Duh.
RajeevBhatt wrote:
Performance
This is a meaningless statement.
RajeevBhatt wrote:
, that would comprise of an Oracle database
Then why did you ask about data persistence ?
RajeevBhatt wrote:
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.
Sounds to me like you read an old copy of MSDN on the toilet while waiting for someone to accept your rentacoder bid, and you know lots of buzzwords and not much about programming.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
RajeevBhatt wrote:
Winforms Vs ASP.NET?
Definitely WinForms if you want it to be a thick client app (Or you could use WPF). Go for ASP.net if you want it to run in a browser.
Communication
Yes, I would include some.
Data persistence
Probably a good idea, but not necessary if your users have very good memories.
Performance
The faster you make it the better.
Any other criterion that you might consider important.
It shouldn't crash too much if possible.
Simon
Simon P Stevens wrote:
Data persistence Probably a good idea, but not necessary if your users have very good memories and can type very quickly.
FTFY!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
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
Cross Post from VB Forum! Very Naughty. :)
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
-
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
I don't know why, but I always laugh when someone combines the two phrases "enterprise application" and "vb.net", and then, when it really dawns on me that it just persists the notion that VB.Net is a viable development platform, I throw up a little in my mouth.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001modified on Monday, May 10, 2010 11:02 AM
-
Do you have actual functional requirements for this thing or just a list of technologies you want to use?
Josh Gray wrote:
Do you have actual functional requirements
Yeah - it's not VB...
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
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
Hello, my name is Rajeesh, the incompetent SW engineer, who is now shitting himself because he actually has to design something instead of talking about how good he is all day. If you cant do the job then bugger off and do something else, like be a pharamacist, or something. But dont ecpect us to design your crappy product for you.
Morality is indistinguishable from social proscription
-
Hello, my name is Rajeesh, the incompetent SW engineer, who is now shitting himself because he actually has to design something instead of talking about how good he is all day. If you cant do the job then bugger off and do something else, like be a pharamacist, or something. But dont ecpect us to design your crappy product for you.
Morality is indistinguishable from social proscription
fat_boy wrote:
But dont ecpect us to design your crappy product for you.
Yeah, but, your still going to design my crappy product for me right? I mean, I haven't even thought of the product yet and I'm not even going to write the thing once you've come up with the idea and then designed it. By then you'll have invested so much into it you may as well write it for me. Then just ship the working product, with website and marketing sorted to me and we'll all be happy.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
fat_boy wrote:
But dont ecpect us to design your crappy product for you.
Yeah, but, your still going to design my crappy product for me right? I mean, I haven't even thought of the product yet and I'm not even going to write the thing once you've come up with the idea and then designed it. By then you'll have invested so much into it you may as well write it for me. Then just ship the working product, with website and marketing sorted to me and we'll all be happy.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
Yeah. I cant believe people here actually help these lazy bastards. If you cant properly form the question, you havent thought hard enough. And when you do define the quesiton you have almost answered it. I have a mate who is a PM for a big European firm. THey have had increasing targets to offshore their product developement. And the product has increasing got worse and worse.
Morality is indistinguishable from social proscription
-
RajeevBhatt wrote:
Winforms Vs ASP.NET?
If you can't decide this based on client needs, then you're too stupid to write this thing, just like you're too stupid not to cross post this question.
RajeevBhatt wrote:
Communication
I suggest you try doing this with your client, yes
RajeevBhatt wrote:
Data persistence,
Oh, flat files, CSVs for sure. Duh.
RajeevBhatt wrote:
Performance
This is a meaningless statement.
RajeevBhatt wrote:
, that would comprise of an Oracle database
Then why did you ask about data persistence ?
RajeevBhatt wrote:
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.
Sounds to me like you read an old copy of MSDN on the toilet while waiting for someone to accept your rentacoder bid, and you know lots of buzzwords and not much about programming.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
If you can't decide this based on client needs, then you're too stupid to write this thing, just like you're too stupid not to cross post this question.
:thumbsup:
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server. -
Yeah. I cant believe people here actually help these lazy bastards. If you cant properly form the question, you havent thought hard enough. And when you do define the quesiton you have almost answered it. I have a mate who is a PM for a big European firm. THey have had increasing targets to offshore their product developement. And the product has increasing got worse and worse.
Morality is indistinguishable from social proscription
Yes, but when am I going to get my bright new shiny product?
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
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:
bearing in mind that we would like to have a multi-tier application, with a thin client, and 1 to n business/persistence layers.
Well, if you want multi-tier, you should make sure there's a computer on every floor of the building. Networked is optional. Thin client: hmmm, I think you're violating some discrimination laws there. 1 to n business / persistence layers: Definitely seems like your primary customer should be the government then, as gov't's have nearly infinite layers and save everything. I would suggest you look at the IRS for a good business model example.
RajeevBhatt wrote:
The application would be used by users who might be geographically separated.
Yeah, that's sort of problem in this universe. We can't occupy the same space at the same time.
RajeevBhatt wrote:
Your inputs would be highly appreciated.
Awwww. I feel so good! Marc
-
RajeevBhatt wrote:
Winforms Vs ASP.NET?
Definitely WinForms if you want it to be a thick client app (Or you could use WPF). Go for ASP.net if you want it to run in a browser.
Communication
Yes, I would include some.
Data persistence
Probably a good idea, but not necessary if your users have very good memories.
Performance
The faster you make it the better.
Any other criterion that you might consider important.
It shouldn't crash too much if possible.
Simon
Simon P Stevens wrote:
It shouldn't crash too much if possible.
Avoid
option strict onthen. :laugh:Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
If you want my opinion or comment, ask in a forum or on my profile page; I will not participate in frackin' Q&A
-
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
Would "...yes..." be a good enough answer?
My plan is to live forever ... so far so good
