Prophet: On holistic analysis of microservice applications
summary
Prophet reconstructs whole-system architecture by analyzing each service and then fusing results into a canonical context map that merges data models (NLP-based field matching), REST interactions (URL/type/parameter matching) and deployment descriptors. It runs on source or bytecode for Java and Python, can extract JARs by mounting docker socket from Kubernetes containers, and flags 11 microservice bad smells plus five RBAC violation types via combined REST+method-call graphs, producing communication diagrams and aggregated domain/context maps for CI/CD and ops use.
AI-written summary · about
chapters (20)
- 0:00Prophet: On holistic analysis of microservice apps
- 2:45Holistic Picture, Why?
- 5:42How Prophet merges microservices
- 6:41How to Merge Microservices?
- 7:18Canonical Model - from the Bounded Contexts
- 7:56REST Interaction Among Microservices
- 8:38REST Interaction for Containerized Microservices
- 9:41Interpreting SAR
- 11:01Software Architecture Reconstruction (SAR)
- 16:04Prophet's SAR visualization
- 18:16Communication Diagram
- 20:45Visualization: Future Steps
- 22:44Example uses of Prophet's SAR
- 22:58Secure Endpoint Enforcements RBAC Inconsistency
- 25:06RBAC Inconsistency - Detection
- 25:57RBAC Inconsistency Combined Method Call Graph
- 26:51RBAC Inconsistency - Aggregation and Reduction
- 33:22Microservice Code Smells Catalog
- 38:33Extending Static Application Security Testing
- 40:51Community Outreach
related talks
42mMicroProfile: microservices made easy
36mA practical tale of assessing a Microservices Architecture
37mKnee Deep in Microservices
52mWhat Does a Good Microservice Architecture Look Like?
38mMicroservices, a bittersweet symphony
39mObservable microservices
32mBuild a 12-factor microservice using MicroProfile
47mBuild a 12-Factor Microservice with MicroProfile