Case Study: Lending Club achieves real-time microservices visibility and automated deployments with Neo4j

A Neo4j Case Study

Preview of the Lending Club Case Study

Lending Club - Customer Case Study

LendingClub’s DevOps team faced rapid growth of microservices (from 5 to 139) and struggled to meet audit, compliance and operational needs because information was scattered across Jenkins, load balancers, VMs and other tools. Jenkins couldn’t provide real‑time API access or a queryable database, so engineers lacked the visibility needed for service discovery, deployments and impact analysis.

They built “MacGyver” to collect data from GitHub, AWS, Splunk, vCenter, load balancers and more, and persisted a graph model in Neo4j mapping virtual services → pools → virtual servers → app instances → hosts → storage. That combo enabled fast Cypher queries for app check‑in, blue‑green deployment validation, single‑point‑of‑failure detection and automated alerts, replacing spreadsheets with real‑time visibility, faster deployments, improved onboarding and proactive impact analysis for security and operations.


Open case study document...

Lending Club

Ashley Sun

Director of DevOps


Neo4j

166 Case Studies