InteGraph
Abstract
We often concentrate on solutions for complex problems and ignore simple solutions for tedious problems. Given an attention these low hanging fruits shall save time and energy for team and organization.
Problem Statement
Outdated architecture diagrams: It is tedious to keep diagrams up to date and there is repetition of work across multiple teams and most of the cases team level/enterprise level architecture diagrams do not reflect up to date design and architecture.
Different environment mappings: When an application is integrated with applications in different business groups or outside organization we come across scenarios where environment mapping becomes complicated. Other application may not have similar environments that we have. While performing integration testing user has to rely on document or SME to understand the flow of data across environments.
Tracking Dependent applications: In service oriented or message oriented architecture it may not be easy to identify integrated systems unless all applications follow specific standard or registered in a service registry. But entire information may not be available from single source.
Application Ownership: If application owner do not maintain appropriate documentation it is difficult to identify the owning team and their contact details. When application ownership is moved to different teams, it is difficult to identify previous owners.
Scattered information: Application relevant information like environments, services, messages, urls, code repositories, setup instructions are spread across different locations. Standardizing and making information available at single location, shall save time and energy.
Solution
A web based application(InteGraph) backed by graph database like Neo4J and graph visualization tools shall in help in maintaining up to date architecture diagrams. By giving appropriate privileges each team should be able to update its own application integrations. With the help of features like filtering we should be able to see specific integrations. Graph databases also provides ability to track entire connected chain thus helping to visualize data flow across multiple systems.
With InteGraph environment mapping diagram shall look like
Leveraging the power of Graph Data Base, properties can be added to both Nodes and Relationships.
To visualize all the systems connected with MyApp:Stage, a simple query can be executed and result can be shown as below
By selecting a particular node or relationship, user can be shown application related information like hostname, url, port.
Conclusion
Leveraging the power of people and graph database, up to date Application Integration Architecture Diagram, can be a ‘reality’.
Note: InteGraph is an imaginary application name and I do not have any association with any company with the same name. Having experience in designing and developing multiple content management systems and being inspired with OASIS TOSCA and OpenCypher I came up with customizable and easily manageable solution. As I like Neo4J, my inclination is towards Neo4J.
