Picking the best, if not correct, technology for many SaaS (Software as a Service) start-ups can be a very tricky endeavour.Many times the business side of the fence does not care or does not know to care what implementation technologies are used during the early stages of a company.They just want a marketable product to start driving market penetration and revenue. However, choosing poorly can lead to the degradation of the SaaS product's supportable, maintainability and scalability down the road which will impact the all important market penetration and revenue efforts.For the most part picking the correct implementation technologies and language is an exercise in risk management and risk mitigation.You want your chosen technologies to be as simple as you need them to be to allow for rapid product development, but as complex, versatile and scalable as your future business dreams may be.Below is my advice on which implementation languages to use and avoid ... and why.
Lets all say this together: "You primary job as an IT professional is to enable the business".This is done by building scalable architectures that are as simple as they need to be, but that complex as what you may need them to be in the future.In order to do this it is very important to pick the correct technologies.Contrary to what you may think there are really only two implementation language options to choose from when deciding on a programming language.It is either Java (Java EE) or Microsoft's .NET (DOT NET).All other languages such as PHP, Python, Ruby, Node JS should be avoided for a number of reasons.
