| There are several things I might consider, but this is by no means an exhaustive list: * Tech fit -- how does this technology solve the business problem? Have you considered how the overall architecture will look like? You might end up splitting them up to several different components each potentially valid to be written in different languages, depending on their nature. Given that, what do you need to achieve? Perhaps a Rails app is fit for purpose if you're writing a proof of concept. Or you might opt for a language that has established libraries for exposing a RESTful interface and write an SPA on top of that. My point is that it really depends on the business problem and how that is tackled. * Ecosystem -- are there libraries out there that help you do what you need it to do? Will you have to roll your own? * How will it be maintained? If you're not working for yourself, then you can assume your code will be maintained by someone else. Is the technology chosen accessible for your intended audience? Like you said, if it is a xyz shop, then it might make sense to write it in xyz. If it's a polyglot shop, then perhaps this is less of a consideration. * What are the development tooling like? IMO this is quite important for my sanity because I dislike using clunky tools. * How will the code be pushed out to production. Are there established best practices for pushing the code you're written in xys language into production? * How easy is it to write tests for the language? Something to also consider is whether it is good for the future. There is an element of YAGNI here, but it's worth considering the longevity of your technical choices and how easy it will be to upgrade. |