I think one important point is not to try to do too much inside the thesis. As it is scientific work, there has to be a lot of research and the state of the art and your research has to be documented. Also, your code needs to be covered by the thesis. If you have 6 months on the thesis, the programming part should be 6-8 weeks of that, so the time is limited.
Then you could see which areas the professor that will host your thesis is interested in, maybe he or she also has an idea that matches your interests. And though it should not be this way, a topic that is aligned with the research if the prof often makes it easier.
Though it may sound boring: a master thesis does not require original research, so you don't have to do something completely new. You also don't have to succeed, so trying something and failing for good reasons is fine as well.
So if you are interested in microservices and architecture, you could see if you can play with the CAP theorem, i.e. build a distributed database, where the user can configure which of the three the user wants to drop. Or you could analyze time assertions for a distributed system of your choice (guaranteed response times or x% of the requests respond within 1000ms). You could also think about a new way to measure and evaluate availability of a distributed system, a bit like Google did with their error budget.
I hope this helps a biz in your way finding a topic for your thesis!
you're probably right. I guess I do put a little too much into the thesis and I guess that's really not necessary :). Unfortunately my professors are not really a big help in finding a topic... I have the feeling that they are more focused on the full time students rather than the distance learning, part time students...
You're topic idea sound really good, though. I'll look into those! Thank you so much!
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.
I think one important point is not to try to do too much inside the thesis. As it is scientific work, there has to be a lot of research and the state of the art and your research has to be documented. Also, your code needs to be covered by the thesis. If you have 6 months on the thesis, the programming part should be 6-8 weeks of that, so the time is limited.
Then you could see which areas the professor that will host your thesis is interested in, maybe he or she also has an idea that matches your interests. And though it should not be this way, a topic that is aligned with the research if the prof often makes it easier.
Though it may sound boring: a master thesis does not require original research, so you don't have to do something completely new. You also don't have to succeed, so trying something and failing for good reasons is fine as well.
So if you are interested in microservices and architecture, you could see if you can play with the CAP theorem, i.e. build a distributed database, where the user can configure which of the three the user wants to drop. Or you could analyze time assertions for a distributed system of your choice (guaranteed response times or x% of the requests respond within 1000ms). You could also think about a new way to measure and evaluate availability of a distributed system, a bit like Google did with their error budget.
I hope this helps a biz in your way finding a topic for your thesis!
Hey Philip,
you're probably right. I guess I do put a little too much into the thesis and I guess that's really not necessary :). Unfortunately my professors are not really a big help in finding a topic... I have the feeling that they are more focused on the full time students rather than the distance learning, part time students...
You're topic idea sound really good, though. I'll look into those! Thank you so much!