Contact

Data integration

GP Data Gateway

In production

A single gateway gives corporate applications access to operational data from 48 dealership locations without direct database connections.

Problem

Each dealership location runs its own DMS instance. Retrieving data across the group required configuring access to every instance separately, and each new application repeated the same work.

Solution

The gateway centralizes connections to all 48 dealership locations and publishes an operation catalog. An application specifies the operation and location, then receives the result without managing connection details or writing queries.

Outcome

Applications query 48 dealership locations through one consistent interface. New operations can be added without changing the applications that use the service.

My role

I designed and built the central service, operation catalog, application-level access controls, and deployment within the group’s network.

How it works

The consuming application specifies an operation and location; the gateway resolves the connection and returns a consistent response.

Scroll horizontally to view the full diagram.

Centralized DMS request and access architecture An authorized application runs one defined operation against one dealership location per request. The administration area maintains the operation catalog, clients, and location directory. ADMINISTRATION REQUEST EXECUTION EXTERNAL SYSTEM DEFINE REGISTER AND TEST CHECK PERMISSION DEFINITION REQUEST VALID RESOLVE LOCATION CONFIGURATION EXECUTE DATA STANDARD RESPONSE ADMINISTRATOR Manage access Clients and permissions CONFIGURATION Operation catalog Type · timeout · limit DIRECTORY Dealership locations Code and encrypted credential CONSUMER Internal application Operation and location ACCESS Access control API key and permission CONTRACT Validate parameters Names, types, and values GATEWAY Query executor Parameterized operation TARGET Selected DMS One SQL Server instance REQUEST RESPONSE / CONFIGURATION DMS ACCESS
Each request targets one dealership location and returns the same response format. Administrators publish operations and access rules without changing the applications that use the service.

Key functions

Technical details

Technology
NestJS 11 · TypeScript · TypeORM · Node.js 24 LTS
Databases
PostgreSQL for the catalog · SQL Server at dealership locations
Runtime
Windows service on the group’s network, with automatic restart
Coverage
48 dealership locations · 15 brands · configurable operation catalog