Request Transformation Layers

In this lesson, you will learn how to create a "Request Transformation Layer" to ensure your internal business logic always receives data in a consistent, predictable format.

Why Transform Data?

As your application grows, the clients consuming your API—or even different versions of your own frontend—might send data in slightly different ways. For example, one client might send a date as YYYY-MM-DD, while another sends it as a Unix timestamp. If your controller logic has to account for every possible input variation, your code will quickly become bloated and fragile.

A Request Transformation Layer acts as a bridge between the raw req.body and your controller. It intercepts the request, maps the incoming keys to your internal domain model, and formats values into the structure your application expects.

Implementing the Transformation

Think of this as a middleware function that runs immediately after your input validation pipeline. By the time the request hits your controller, the "messy" external format has already been converted into a clean internal object.

// A simple transformation middleware
const transformUserRequest = (req, res, next) => {
  // Normalize incoming "user_name" or "username" to "fullName"
  const raw = req.body;
  
  req.internalData = {
    fullName: raw.user_name || raw.username || 'Anonymous',
    isActive: typeof raw.active === 'string' ? raw.active === 'true' : !!raw.active,
    processedAt: new Date().toISOString()
  };
  
  next();
};

// In your route
app.post('/users', transformUserRequest, (req, res) => {
  // Controller only deals with req.internalData
  userService.create(req.internalData);
  res.status(201).send();
});

The Benefits

1. Decoupling: If your database schema or internal naming convention changes, you only update the transformation logic, not every controller in your system.
2. Readability: Your controllers remain lean, focusing strictly on business actions rather than data cleanup.
3. Consistency: You eliminate conditional checks like if (data.x || data.y || data.z) throughout your entire service layer.

By placing this transformation before your controller, you treat your internal logic as a "clean room" where only validated, normalized data is permitted to enter.

Key Takeaway: A Request Transformation Layer shields your business logic from messy or inconsistent external input formats by normalizing data structures into a standard internal format before they reach the controller.