i'm going to try and start developing some software i have had planned out for a while. i was wondering if anyone could give me some info on which platform i should go with...heres some info:
application 1) deals with scheduling appointments. uses calDEV to transport calendar data from the server (which hosts an online cal) and the client devices (PDA, outlook, etc.) main interface will be web-based while simpler viewing/editing of calendars will be done with the customer's remote software.
application 2) databases collection information and stores lots of images. will connect to a main server to update a DB that stores collection information (makes, models, etc.) and current market prices. the main interface will be web based, however, i'm thinking about writing a complimentary front end in VB.net, C#, or Java
application 1 is targeted at a large market and if it were to explode, the server load could be quite significant, but dependent upon how many users there are. however, part of my marketing plan is to run multiple companies on one of my hosted machines, so, potentially, it could be quite the load. It will also be interacting with a mail server to send alters and what not. Furthermore, it will be tied to a shopping cart of some sort. the goal with this application is for it to be robust, quick, and never go down...ever. cost should be minimized, but customers would be willing to pay for MS software if the product delivers.
application 2 will not require a lot of performance as it will likely never be used by more than 1-3 users at a time. the more important goal with this application is for it to be cheap, very cheap.
here is the deal, i am a bit familiar with MSSQL (at least the management of it) and know nothing about MySQL or its management tools. I don't know PHP or ASP hardly at all, but i do know C++, Java, and VB so the transition to either wouldn't be too bad, or, so i think.
anywho, i really want to do both programs on the same platform. currently, i see the following benifits/advantages for both platforms:
ASP/MSSQL:
PRO:
-i understand msSQL better and will know it well after my class this semester
-it is supported corporately
-it is highly reliable
-it can be cheap if the user base is small
-i understand and enjoy MS IDEs
-included support
CON:
-it isn't cheap for large situations
-it isn't muli-platform
PHP/MySQL:
PRO:
-Open source, so it is free and tons of extensions and libraries
-it is multi-platform
-very good performance
-very simplistic email libs
-should be easy to implement calDEV
CON:
-have to learn how to use a new IDE (not really that bad)
-have to learn how to use MySQL and its management tools
-Requires more initial configuration
-May have to worry about open source licensing in the future (might have to pay royalties)
-support isn't cheap (unless you depend on forum users)
application 1) deals with scheduling appointments. uses calDEV to transport calendar data from the server (which hosts an online cal) and the client devices (PDA, outlook, etc.) main interface will be web-based while simpler viewing/editing of calendars will be done with the customer's remote software.
application 2) databases collection information and stores lots of images. will connect to a main server to update a DB that stores collection information (makes, models, etc.) and current market prices. the main interface will be web based, however, i'm thinking about writing a complimentary front end in VB.net, C#, or Java
application 1 is targeted at a large market and if it were to explode, the server load could be quite significant, but dependent upon how many users there are. however, part of my marketing plan is to run multiple companies on one of my hosted machines, so, potentially, it could be quite the load. It will also be interacting with a mail server to send alters and what not. Furthermore, it will be tied to a shopping cart of some sort. the goal with this application is for it to be robust, quick, and never go down...ever. cost should be minimized, but customers would be willing to pay for MS software if the product delivers.
application 2 will not require a lot of performance as it will likely never be used by more than 1-3 users at a time. the more important goal with this application is for it to be cheap, very cheap.
here is the deal, i am a bit familiar with MSSQL (at least the management of it) and know nothing about MySQL or its management tools. I don't know PHP or ASP hardly at all, but i do know C++, Java, and VB so the transition to either wouldn't be too bad, or, so i think.
anywho, i really want to do both programs on the same platform. currently, i see the following benifits/advantages for both platforms:
ASP/MSSQL:
PRO:
-i understand msSQL better and will know it well after my class this semester
-it is supported corporately
-it is highly reliable
-it can be cheap if the user base is small
-i understand and enjoy MS IDEs
-included support
CON:
-it isn't cheap for large situations
-it isn't muli-platform
PHP/MySQL:
PRO:
-Open source, so it is free and tons of extensions and libraries
-it is multi-platform
-very good performance
-very simplistic email libs
-should be easy to implement calDEV
CON:
-have to learn how to use a new IDE (not really that bad)
-have to learn how to use MySQL and its management tools
-Requires more initial configuration
-May have to worry about open source licensing in the future (might have to pay royalties)
-support isn't cheap (unless you depend on forum users)