Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
At the end of the day, languages aren't going to matter too much unless you have corporate policy that dictates you must use some ancient version of language X. A language is just a tool, and for the most-part, the majority of languages will be able to produce a solution; some will be easier than others and some will be more elegant, some will offer you no community support and some of them will have a vibrant community willing to help you out. Pick what you are most comfortable with.
We can buy more hardware to deal with slower languages, or implement cache services. Over time, you can refactor parts of the application into microservices if you need to use one specific language for some unique functionality.
It sounds like you are writing a pretty cool app that will involve a lot of moving pieces. There are a lot of design questions you need to answer and the good news is that you don't have to answer them in a computer language! Working code is the most valuable kind of code out there. Use whatever it takes to produce that. It's great that you have thought ahead and identified possible bottlenecks, but you'll never have a chance to encounter them if you get stuck with analysis paralysis!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
At the end of the day, languages aren't going to matter too much unless you have corporate policy that dictates you must use some ancient version of language X. A language is just a tool, and for the most-part, the majority of languages will be able to produce a solution; some will be easier than others and some will be more elegant, some will offer you no community support and some of them will have a vibrant community willing to help you out. Pick what you are most comfortable with.
We can buy more hardware to deal with slower languages, or implement cache services. Over time, you can refactor parts of the application into microservices if you need to use one specific language for some unique functionality.
It sounds like you are writing a pretty cool app that will involve a lot of moving pieces. There are a lot of design questions you need to answer and the good news is that you don't have to answer them in a computer language! Working code is the most valuable kind of code out there. Use whatever it takes to produce that. It's great that you have thought ahead and identified possible bottlenecks, but you'll never have a chance to encounter them if you get stuck with analysis paralysis!