Large Application - Web Based - Platform/Language Suggestions

Associate
Joined
10 Apr 2004
Posts
839
Hi All,

I've been given the potential task for a very large scale application (full blown ledgers, e-commerce etc.)

I'm an old school programmer and basically for this project will be managing/design rather than me getting my hands dirty (outsourcing most likely).

One of the initial requirements is that its web based rather than fat clients or running via terminal services etc. The formost suggestion at the moment is .NET platform, SQL and using c#/vb go ASP. The thinking is easiesr to outsource, big names etc...

Its a custom application (quite specific) so I can't really bring in 3rd party stuff and attempt to integrate especially as consistent look/feel would be best.

Any thoughts?
 
Thanks guys,

From discussing with various friends etc I have other suggestions such as PHP, MySQL/Oracle, Rails

Its easier to pitch a solution with industry names that are well known/supported, might be pro's and con's but a better overall fit (resource etc).
 
So it looks like c# and SQL is the best bet (doesn't suprise me).

Whats the thinking regarding the organisation.

2 Tier
Web Client (but fat with presentation and business processing)
Database SQL and use all the new features (like embedded c#/vb).

3 Tier
Web Client (ASP)
Business Processing (c#)
Database SQL (and still use the features because business layer serves data).

I'm really looking for peoples opionions or what they have experienced or had issues with. Just looking to make sure an suggestions can be made and not go down a route which could be fraught with issues.

Cheers
 
Thanks for all that guys much appreciated.

In terms of its size I guess its in the 100's of users so I would assume medium size application.

I'll deffo get hold of that book.
 
Cheers for the info so far :D

Current application is an old legacy Unix product (that I maintain - scale dictates any new project would not be developed by myself and would be outsourced somewhere in the world).

New product is prefered to be Windows based (pretty much closed viewpoint unfortunately). My questions are mainly because the push seems to be IIS,.NET - C#,SQL 2005

I think its a stigma that certain companies have MS tatto'd on their forehead and just won't even attempt to consider the open source routes for anything. I can try hard but I fear in my case it would be a lost battle before I started.

Regarding some of the above points.

System is 24/7 so I had already realised that it would need to be clustered etc. We already have resiliancy in place now so its a given.

I do need to investigate license costs - for example if you have say 150 users at the actual site using the system but maybe 100's using the e-commerce section (same full application just locked off functionality as such) I then need to see how it impacts on cost (is it per seat, per concurrent user, per CPU, per whatever. I have already seen the costs of some of the MS ERP solutions so I know nothing is going to be cheap :cool:

I know the costs involved are high (hardware, s/w/ licenses, time etc) and the continuing maintenance costs will not be cheap (support team etc.)

Many thanks you've definately given me more food for thought.
 
Back
Top Bottom