<img alt="" src="https://secure.leadforensics.com/149263.png" style="display:none;">
hero wave

Analyzing Application Code for Potential Microservices [Video]

Want to modernize your application to microservices, but don't know where to start?

Eric Minick (VP, Head of Product) explains how to use the CodeLogic Desktop Client to examine an application and see if it might be appropriate to break down into fewer services. Using an open-source IoT application called ThingsBoard, Eric utilizes the Hierarchic Layout to see the Java code content toward the top and the data elements down toward the bottom, revealing how the application fits together. 

Examine the application

To see if an application can be cut into microservices, Eric looks for significant decoupling at a data layer. If many classes from across the application are connected to the same columns it will be more difficult to unwind than if the beginnings of a domain approach are already apparent. In general, vertical connection clusters look very promising, versus diagonal connections which cause more concern.  

Understand the diagonal lines

In this video, Eric uses CodeLogic's interactive legend to walk you through how to understand the application's diagonal lines, which imply coupling, to see if they're fundamental to the application or if they're something that can be managed. 

The takeaway

As you begin exploring and analyzing a new application to see what could be broken out into microservices, look for vertical stacks that could be split into a logical domain and that don't directly touch the data, so you can better understand where to group and decouple your code from there. 

For more information or to schedule a free Demo, contact us today!

Want to learn more about dependency mapping?

Browse Blog