Choice of development tools for the server side?

Question

Java

Good day. I am writing my thesis. It consists in developing a ticket system (something like a taskboard). It consists of client and server parts. The client will be an android application. The task of the server part is to process requests from the client, catch information from the database (MySQL) and send it back, everything is simple. The essence of the question is the rationale for the choice of language for writing the server side. I would like to use Java (since I know it better and plan to develop further in this direction), but "I know it better" is not an argument. How can you justify the choice of Java for the development of the server side (analogues: php, C #, etc.)? Thanks in advance.

Answer 1

In general, of course, the fact that it is more interesting and easier for you to make a project in Java should be decisive in this case . But you can find other reasons as well.
For starters, the fact that in your plans to develop a client for android, for which you will probably use java, that is, from the obvious advantages, you do not have to understand two different languages ​​\u200b\u200bto create both parts of the project. It also allows you to reuse some code in both parts. Additionally, you will be using the same tools for both projects - Android Studio is the official IDE for creating android applications, it is based on IntelliJ IDEA - one of the best IDEs for java.
Well, more standard reasons for choosing jvm and java:
- A lot of high-quality and free tools
- A lot of high-quality libraries and frameworks - both old, time-tested, and new ones that implement fashion trends
- A lot of examples, books, manuals, video reports, and so on
- Cross-platform
- Static typing - less likely to shoot at leg
- Reliable platform in terms of project growth
- and so on
I think this will be enough to explain the choice of language for the graduation project. But in a real project, the choice will depend on many more factors, on the vision of the development of the project, on the architectural solution, on how much the team is ready to work productively with the chosen language, or on how easy it will be to find a developer for this language and many more specific nuances. Well, do not forget about the now popular microservices, where different services can be written in different languages.
Finally, a small recommendation. As tools for implementing the server side, take a look at the Spark Framework (this is a micro web framework, not to be confused with Apache Spark) - to create a REST interface and JOOQ to communicate with the base.

Answer 2

It can only be based on your personal preference.
If you are not doing any real research that challenges you to write on something, then write on something that will be easier for YOU.