Build an enterprise application for a customer with aprox. 100 Clients ???

edited March 2004 in Science & Tech
Build an enterprise application for a customer with aprox. 100 Clients ???

HI!!!

If you would happen to get the chance to build an enterprise application
for a customer with aprox. 100 Clients (…and increasing) which technology
and architecture would you choose. The security policy is pretty strong
so we would have actually only port 80 available. Besides that no deployment
effort on client side is desirable. There is a 100Mbit LAN and this new
application would be deployed on the intranet (internal network).
The GUI of this application should be very rich and fast like win32 applications.
What would you propose in order to fulfil those requirements.

It is an enterprise app… so inputing data, printing invoices,
packing lists, reporting, etc
Clients are win xp machines It processes data on the server mainly,
the presentation is on the clients Data is stored in a database
100Mbit has to do with the access speed to the backbone resources
from clients.(only port 80)

Any hints, links and ideas will be highly appreciated



Regards,



gicio

Comments

  • kryystkryyst Ontario, Canada
    edited March 2004
    I would go drop a whole whack of money and not be stupid about it and by a propper enterprise software. Trying to design one yourself is a huge undertaking and you can't even begin to fathom how things are all related to each other. If you want realtime inventory management customer service tracking, call center tracking, Scheduling the list goes on and on. It's a ridiculous thing to just assume you can whip up. There are entire corporations who's soul purpose is designing this type of software. It's not a weekend project. Be realistic and no when to tell who ever is giving you the pinch to pull their head out of their ass and be realistic.

    The money you spend up front in buying real software with real support will save you 100 fold when your hacked together system crashes and you loose data. Think how much time it would cost you if you loose 1 days worth of transactions if they had to be re-entered. Then figure you are now down at least 2 days for every day you've lost. Now picture this all failing and having every person in the company blaming you because the software you designed crapped out. To say you'll be out of a job is an understatement.

    But if you want to live your own personal hell and try and develop some software. I'd recommend using a mysql backend with PHP as the web interface to it. That's about as free and as stable as you can get. With support for multiple simultaneous transactions going on at once.
Sign In or Register to comment.