Please log in to watch this conference skillscast.
During this talk you will learn:
How to keep a self-actualising map of all these entities and how they depend on each other.
How to best expose and leverage such a map to improve operations, design and refactoring.
BritishGas approach takes data from both automated static analysis tools and live tracing & traffic sources; all combined to generate and keep an up-to-date graph of components and dependencies. A neo4j graph then used by other tools to, for example:
automatically list the endpoints and journeys impacted when a third party system is down, and notify the relevant teams,
help with bug investigations and assist in understanding the root cause of multiple problems,
list what consumers, front-end and back-end, will need re-testing when an endpoint is being refactored,
provide clear maps and graphs to architects, managers and developers, promoting better communication between teams,
detect certain duplications, coupling and other anti-pattern issues, helping toward a better architecture.
YOU MAY ALSO LIKE:
Lightning Talk: Microservices and Dependency Mapping - How to Obtain and Leverage the Graph of the System Component Interactions
Mikael is a Senior Developer at British Gas. Backend & Frontend, Microservices, APIs, AWS, iOS/Mobile apps, Architecture, Technology enthusiast. Twitter: @Mikael_wozniak