|
Hello!
I hope this is the right section for this type of question. What would be the better route to go for a new enterprise web application from the following (if I missed something or seem confused on something, please fill me in).
1) ATL/ASP.Net & MSSQL
2) COM/DCOM/ASP.Net & MSSQL
3) ASP.Net (C#/VB.Net) & MSSQL
4) PHP/MySQL
We are looking to be able to scale from 10 users to 50,000 users, and a good secure base. Though, I do code, I am not an expert when it comes to enterprise applications. Our competitors are using COM and ASP/JSP, another competitor is using VB.Net/ASP.Net.
Best,
Mike
|
|
|
|
|
There's no real easy way to answer this question. It really gets down to what you are trying to do. For instance, are you going to be exposing web services? Are you going to be consuming data from other data sources? What timescales/expertise do you have to develop in?
I would rule out option 2 though. That way lies pain and misery
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
We will have a database server, an application server and a web server. We only want top expose the web front end. It will basically take data from the database server, and have some business objects on the application server to use.
|
|
|
|
|
Is there any problems just stuffing all of our business code/sql code in a MFC DLL and calling the DLL using ASP.Net?
|
|
|
|
|
If you're doing it with ASP.NET, then why aren't you considering using C# or VB.NET?
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
|
ASP.Net C# & MSSQL - best way 2 go
|
|
|
|
|
How do I depict decision-branching in a sequence diagram? Can anyone provide a simple example (maybe a simple drawing) where an object makes two different calls /sends two different messages or events depending on a decision within its function or thread of execution.
Thank you!
I am a SysAdmin, I battle my own daemons.
|
|
|
|
|
I don't have any reference material with me, but as far as I recall you use a block with a guard condition around all the messages within each variant of the decision outcome.
|
|
|
|
|
DenClancy wrote: How do I depict decision-branching in a sequence diagram?
There is no IF or ELSE in a (UML) sequence diagram, AFAIK. If you want to depict decision-branching just draw multiple sequence diagrams, one for each branch.
|
|
|
|
|
Exactly.
I don't think Sequence diagrams are supposed to depict if / else.
Infact, for any if and else you need to have a new sequence diagram.
Thats the whole intenet of a sequence diagram.
|
|
|
|
|
perhaps you need an activity diagram.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
|
|
|
|
|
Anybody has any experience with the above?
I'm curious if this really speeds up project development or just ads
a layer of complexity
-- modified at 2:26 Thursday 8th March, 2007
company, work and everything else @ netis
|
|
|
|
|
Just out of curiosity why is someone voting down a post without any reply ?
company, work and everything else @ netis
|
|
|
|
|
because noone has a clue what you're asking about????
--
Rules of thumb should not be taken for the whole hand.
|
|
|
|
|
I know I don't have a clue what dOOdads are or is all about and you've given no links to describe what it is either.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
You're right. dOOdads is a tool for O/R mapping and code generation of data layers.
Here is the link
|
|
|
|
|
We evaluated dOOdads when we looked at MyGeneration, but we ended up going with DevExpress' eXpress Persistent Objects. It fits in better with our client architecture and doesn't require us to fit in with plumbing that doesn't quite match our needs.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
I actually asked another version of this before but this time I am just curious about the .NET to .NET part. I no longer work for the company that was attempting this but it still makes me curious. The company wanted to have a web server, an app server, and the database (SQL) server.
I get the web and database servers, I've done that. What I dont understand is why go through all the trouble to take all of the business logic and place it on an App Server behind the fire wall and only do presentation code on the web server.
How feasible is this with .NET?
They are currently doing this with Classic ASP and VB6 because they have a way to tell the app to use the COM objects on another box or something along those lines but with .NET it seems that you have to have another web server behind the firewall for this to work because you would need to be able to either use a web service or .NET remoting right???
Cleako
-- modified at 9:40 Thursday 15th February, 2007
|
|
|
|
|
Security is the first thing that comes to mind. When dealing with an internet based application you only expose what you absolutely need to. By exposing your presentation layer machine only you given yourself a small amount of risk. Now - no matter how much your server gets attacked - that is the only part of the business that will be affected. If there are other internal machines that rely on the business layer they will be able to use that business layer just fine while your internet users are the only ones having trouble.
Patrick Allmond
http://allaboutfocus.com
|
|
|
|
|
Would this be implemented using the .NET Remoting/Web Service option? It seems to me that if you expose the internal server using web protocols that it could be hacked.
Cleako
|
|
|
|
|
cleako wrote: because they have a way to tell the app to use the COM objects on another box
You could do the same thing with a ASP.NET web service and COM+ business objects. Although I fail to understand the benefit.
led mike
|
|
|
|
|
cleako wrote: What I dont understand is why go through all the trouble to take all of the business logic and place it on an App Server behind the fire wall and only do presentation code on the web server.
That's interesting, because I did some work for a company wanting to do the same thing. However, the reasoning there was to first develop an App server with a rich presentation client, then a web server as merely a different sort of rich presentation "client". In both cases, the business logic would be on the app server.
As to feasible, regardless of what technology you use, it's actually very difficult. They never succeeded. I think it's doable though.
Marc
Thyme In The CountryInteracxPeople are just notoriously impossible. --DavidCrow There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith
|
|
|
|
|
Their thought is that it is safer having the business logic on the app server, but I thought that .NET took care of the security issue by building the code into DLLs.
Cleako
|
|
|
|
|
Isolating the business logic behind the firewall may be an attempt to reduce the attack surface of the application. The risk is that once a web server is attacked, the attacker can then discover the attack path through the firewall.
Another reason to use an n-tier infrastructure is to reduce the load on the web server.
The risk in this scenario is that a performance bottleneck can be created between web server and app server by relatively slow network technology.
.NET remoting does not require the HTTP protocol, and therefore, has no requirement for a web server. One way to think of .NET remoting is an evolution of the COM/DCOM model.
The risk here is that you are restricted to Microsoft technologies on both communication endpoints.
Web services requires a web server, and is restricted to the HTTP protocol.
If you really want to start to understand the ins and outs of n-tier development in relation to .NET, locate a copy of
"Microsoft® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting" by Matthew McDonald copyright 2002
It references ASP.NET 1.x, and it provides examples of how to evolve a VB6/COM application to .NET.
This is an easier said than done process.
HTH,
onemorecoder
|
|
|
|