Volkswagen Group

Paraview API solutions help Volkswagen Group counter the pain points in internal system integration and external data collection.

Overview

Industry

Manufacturing

Business Nature

Motor Vehicle Manufacturing

Company Size

>648k Employees

Services Required

API

The Problem

Internal Pain Points

Core systems are interconnected through numerous interfaces, making it difficult to quickly grasp their interactions and increasing the complexity of operations and maintenance.
Clarifying system interfaces is challenging, often resulting in redundant development and hindering the creation of unified standards to boost operational efficiency.
Identifying issues when interface calls fail is problematic due to the absence of end-to-end tracing, leading to higher operational costs from increased coordination and communication efforts.

External Pain Points

Internal systems offer extensive data push and functionality support, including activity notifications, content processing, and order status updates. The exposure of these customer-facing interfaces to the internet introduces risks of data leakage and unauthorized access.
During promotional activities in stores, user interactions with order signing and delivery confirmation in related systems can create excessive access demands. Without load balancing, prioritization, and throttling, there is a risk of delays or crashes.
One app offers end users a comprehensive solution for the entire vehicle lifecycle. The stability, security, and standardization of these interfaces are essential for delivering a positive user experience and ensuring operational efficiency.

Our Solution

Application Architecture

Include operational platform components alongside integrated third-party services.
The Integration layer is anchored by the API gateway, which facilitates the integration of business systems.
The Service layer encompasses business, middleware, and technology services that require integration.
The Operation layer oversees platform functions such as logging, authorization, and overall management.

Deployment Architecture

Technical platform services are deployed on Kubernetes for high availability, stability, and scalability.
Microservices are structured by functional modules, facilitating easier future upgrades and maintenance.
Technical service integration follows a microservices architecture, enabling the expansion of platform functionality.

Network Architecture

The public cloud open gateway is accessible via HTTPS, with certificates managed by a Cloud Load Balancer (CLB) and traffic secured through WAF (Web Application Firewall) policies.
The internal network is segmented into three layers: DMZ (Demilitarized Zone), K8S Cluster, and Data Layer, each with its own access rules and routing policies for secure service access.
The private cloud is restricted to the intranet and follows a similar structure with DMZ, K8S Cluster, and Data Layer, with access rules and routing policies configured for security.

Security Architecture

The public cloud's open gateway is accessible over the internet and uses HTTPS for secure connections. It incorporates DDoS protection, WAF, and firewall components to safeguard traffic entering the K8S Ingress.
Database access is protected by ACL (Access Control List) policies and NSG (Network Security Group) policies at the data layer, ensuring secure and controlled access to the database.

Achievements

Seamless Integration

Seamlessly integrating business applications to ensure comprehensive sales and procurement data integration throughout the entire business process.

Standardization, Accuracy, and Timeliness

Retrieving and refining business data to improve accuracy and timeliness, while establishing standard specifications to enhance operational efficiency.

High Performance and Efficiency

Achieving high performance and efficiency in integration, with a peak throughput of about 50K TPS and integration of approximately 500 APIs, maintaining an average of 100 TPS per API during peak hours.

More Case Studies

View All