dwops
asked on
Keeping costs down and performance up...
I want to start some kind of discussion about development environments, programming languages and database applications... how broad is that!?!
so, I've begun developing my *future* fortune-500 startup application in ASP.Net with SQL Server...
I'm in the early stages of development on the application. I need it to be scalable and support as many users as possible simultaniously but i have a low budget (as low as possible). We're not talking Ebay traffic, but it needs to withstand some traffic and i don't want to re-write it down the road. Its pretty much simple data collection, storing and displaying.
almost all of my experience is with Microsoft. I use SQL Server, ASP.Net, ASP, and various scripting languages at work. At the same time, this application I'm developing on the side is not nearly the scale of the enterprise app at work.
My question is this, because I don't want to make a mistake I'll regret.
Is ASP.Net / SQL Server the most effective route? I know its expensive and hosting on sites with .Net and SQL Server is also expensive. Perhaps I should consider PHP, ASP or a cheaper database solution than sql server...
I know I'll write a better app if i use the technology I work with every day, but I wonder if this technology isn't a good fit for a small startup on a low budget.
What are your opinions. Whoever contributes quality info or makes good suggestions will get points. if you save me tons of money you get even more points!
so, I've begun developing my *future* fortune-500 startup application in ASP.Net with SQL Server...
I'm in the early stages of development on the application. I need it to be scalable and support as many users as possible simultaniously but i have a low budget (as low as possible). We're not talking Ebay traffic, but it needs to withstand some traffic and i don't want to re-write it down the road. Its pretty much simple data collection, storing and displaying.
almost all of my experience is with Microsoft. I use SQL Server, ASP.Net, ASP, and various scripting languages at work. At the same time, this application I'm developing on the side is not nearly the scale of the enterprise app at work.
My question is this, because I don't want to make a mistake I'll regret.
Is ASP.Net / SQL Server the most effective route? I know its expensive and hosting on sites with .Net and SQL Server is also expensive. Perhaps I should consider PHP, ASP or a cheaper database solution than sql server...
I know I'll write a better app if i use the technology I work with every day, but I wonder if this technology isn't a good fit for a small startup on a low budget.
What are your opinions. Whoever contributes quality info or makes good suggestions will get points. if you save me tons of money you get even more points!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the MSDE website says that is is satifactory for up to 25 concurrent users, and if you recall, ASP.NET accesses the database as via a single USER (ASPNET).
AW
AW
ASKER
great, so i would just have to worry about developers or DBA's. If i need 23 more developers/dba's then i think the added cost of some sql server licenses will be most welcomed :)
Thanks for your help, i'm going to give some time for alternative voices to be heard...
Thanks for your help, i'm going to give some time for alternative voices to be heard...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
no, i don't have to worry about 25 different simulaneous connections...
the MSDN option is definatly good, I'll look into it.
the MSDN option is definatly good, I'll look into it.
ASKER
thanks everybody, i was expecting the anti-Micro$oft crowd to jump in with MS alternatives...
i did get some great $$ saving tips though. Thanks!
i did get some great $$ saving tips though. Thanks!
ASKER
it sounds like i'm heading down a good path. i have c#.net backend objects and ASP.Net on the front.
i've used MSDE before, the only problem i think could be concurrent connections. I hear MSDE only supports a few so it isn't recommended for web apps.
Other experts, please feel free to continue this discussion, I'm waiting to hear the advantages of some other alternatives