Skip to content

LendingTree Insurance Division Documentation

Welcome to the comprehensive documentation for the LendingTree Insurance Division's Publisher platform microservices ecosystem.

Overview

The Publisher platform is LendingTree Insurance Division's distributed microservices architecture that handles lead generation, campaign management, data processing, and reporting for insurance products. This documentation provides detailed information about each microservice, including architecture, APIs, configuration, and deployment details.

Microservices Architecture

The Publisher platform consists of 30+ microservices, each responsible for specific business functions. All services are containerized and deployed on Kubernetes, following consistent patterns for configuration, monitoring, and integration.

Service Categories

Campaign and Lead Processing

Services that handle campaign validation, lead processing, tracking, and response management.

Data Management and Processing

Services responsible for document operations, data transformation, and source management.

Authentication and Authorization

Services that handle user authentication, authorization, and access control.

Reporting and Analytics

Services that generate, process, and deliver various types of reports and analytics.

Data Processing and Enrichment

Services that enrich data, count events, and perform specialized data processing tasks.

Infrastructure and Utilities

Supporting services that provide caching, routing, healing, and utility functions.

Common Patterns

Architecture Patterns

  • Microservices: Each service is independently deployable and scalable
  • Event-Driven: Services communicate through Azure Event Hubs
  • CQRS: Command Query Responsibility Segregation for data operations
  • API Gateway: Centralized API management and routing

Technology Stack

  • Runtime: Node.js with Azure Functions
  • Database: Azure Cosmos DB, Snowflake Data Warehouse
  • Messaging: Azure Event Hubs, Azure Service Bus
  • Storage: Azure Blob Storage, AWS S3
  • Monitoring: Application Insights, custom logging
  • Deployment: Kubernetes, Docker containers

Configuration Management

  • Environment-specific configurations (dev, int, prod)
  • Centralized configuration through Azure Key Vault
  • Feature flags and runtime configuration updates

Getting Started

For Developers

  1. Browse the Internal > Services section in the navigation to explore individual microservices
  2. Review service-specific documentation for implementation details
  3. Check API documentation and integration patterns

For Operations

  1. Review monitoring and alerting configurations in each service
  2. Check troubleshooting guides for common issues
  3. Understand service dependencies and integration points

Service Health and Monitoring

  • All services include health check endpoints (/live and /ready)
  • Comprehensive monitoring through Application Insights
  • Automated alerting for service failures and performance issues

Contributing

When adding new services or updating existing ones: 1. Follow the established documentation patterns 2. Include comprehensive API documentation 3. Add troubleshooting guides and monitoring information 4. Update the navigation in mkdocs.yml

Documentation automatically generated from Publisher microservices codebase analysis