24.1. Meeting Notes

High-level picture

• Static Analysis of Microservices
  • Why looking at one service at a time is not enough
    • https://github.com/cloudhubs/tms/blob/master/cms/src/main/java/edu/baylor/ecs/cms/controller/CategoryInfoController.java
  • A holistic centralized view is beneficial.
  • Usually extracted via dynamic analysis.
  • We are trying to do the same statically.
  • Source code vs the output of compilation.
  • Context Map & Service View
  • Usages
    • Dependencies between microservices
    • Propagating changes
    • Code smells
    • Architecture degradation
      • How the source code of the whole system changes over time

End goals

1. Extract Context Map & Service View from the TrainTicket microservice benchmark.

• https://github.com/FudanSELab/train-ticket

2. Compare it with the one generated previously without using GraalVM Native Image.
3. Discuss differences.

• Note: Might be hard to predict exactly, let's see how far we can get! :)

Intermediate goals

1. Implement what is necessary to extract Context Map and Service View using GraalVM Native Image.

• Which entities are in a given microservice.
• What are the dependencies between them.
• Which Rest endpoints are available (including their signatures).
• Which remote methods are called from the analyzed microservice.

2. Compare the output for https://github.com/cloudhubs/tms

• Implement a tool (can be a python script for example) to automatically compare two representations against each other.

3. Fix all issues that are not inherent to our approach