Fix your microservice architecture using graph analysis
So, for your brand new project, you decided to throw away your monolith and go for microservices.
But after a while, you realize things are not going as smoothly as expected ;-)
Hopefully, a graph can help to detect antipatterns, visualize your whole system, and even do cross-service impact analysis.
In this talk, we’ll analyze a microservice system based on Spring Cloud, with jQAssistant and Neo4j. We will see how it can be helpful to answer questions like:
do I have anti-patterns in my microservice architecture ?
which services / applications are impacted when doing a database refactoring ?
is my API documentation / specification up to date ?
how to get an up to date visualization of my whole system ?
and more !